explorerlens-workflows-and-mcp

ExplorerLens — Workflows and MCP Skill

Purpose

Use this skill when editing or reviewing GitHub workflow files, repository AI assets (instructions, agents, prompts, skills), or MCP server configuration. Read it fully before touching any .github/ or .vscode/mcp.json file.

When to Use This Skill

• Updating .github/workflows/*.yml files or their companion docs
• Auditing workflow inventory, trigger intent, and job ownership
• Configuring or documenting MCP servers in .vscode/mcp.json
• Adding/editing instructions, agents, prompts, or skills
• Keeping .github/standards/ai-tooling-capabilities.md synchronized

Step-by-Step: Adding a New Workflow

1. Check if a workflow for the same purpose exists: ls .github/workflows/
2. Name the file descriptively: <trigger>-<purpose>.yml (e.g., push-build-engine.yml)
3. Use windows-latest runner for C++ builds — never pin toolset in ilammy/msvc-dev-cmd@v1
4. Use actions/cache with sccache key for build caching
5. Add the workflow to .github/instructions/cicd.instructions.md inventory table
6. Add the workflow to .github/standards/ai-tooling-capabilities.md
7. Test with act locally or push to a feature branch first

# Minimal correct workflow skeleton
name: Build Engine
on:
  push:
    branches: [main]
  pull_request:
    branches: [main]
jobs:
  build:
    runs-on: windows-latest
    steps:
      - uses: actions/checkout@v4
      - uses: ilammy/msvc-dev-cmd@v1  # NO toolset pin — auto-upgrades with runner
      - run: .\build-scripts\Build-MSVC.ps1 -Clean -Test
        shell: pwsh

Step-by-Step: Adding/Editing AI Assets

Instructions (*.instructions.md)

• File: .github/instructions/<scope>.instructions.md
• Must have applyTo: frontmatter scoping it to relevant file patterns
• Update .github/standards/ai-tooling-capabilities.md in the same commit

Agents (*.agent.md)

• File: .github/agents/<name>.agent.md
• Must include: description, tools list, behavioral constraints, example invocation
• Agent names must be unique; avoid generic names like "Assistant" or "Helper"

Prompts (*.prompt.md)

• File: .github/prompts/<name>.prompt.md
• Must include: purpose, inputs, expected output, constraints
• Prompts must be task-specific — do not create prompts for open-ended exploration

Skills (*/SKILL.md)

• Directory: .github/skills/<skill-name>/SKILL.md
• Minimum length: 100 lines with concrete step-by-step procedures
• Must include: purpose, when to use, step-by-step, constraints, validation checklist

Step-by-Step: MCP Server Changes

Adding a New MCP Server

1. Evaluate the need — verify the agent workflow that requires the server. Current servers: github (GitHub API), filesystem (full workspace), project-docs (docs-only).
2. Check for conflicts — ensure the new server doesn't overlap with existing ones.
3. Edit .vscode/mcp.json — add the server entry following this template:

   "server-name": {
     "command": "npx",
     "args": ["-y", "@scope/mcp-server-package", "${workspaceFolder}\\scope-dir"],
     "env": {
       "PATH": "${env:APPDATA}\\npm;${env:USERPROFILE}\\scoop\\shims;${env:PATH}"
     }
   }
   

4. Security checks:
   • Never embed tokens directly — use "${input:token-name}" with "password": true in inputs.
   • Never scope filesystem servers above ${workspaceFolder}.
   • Never add corporate proxy URLs (NO_PROXY, no_proxy, proxy host:port).
5. Test locally — open VS Code, invoke the server via Copilot Chat, verify tools appear.
6. Update 3 inventory files in the same commit:
   • .github/instructions/mcp-servers.instructions.md (server inventory table)
   • .github/copilot-instructions.md (MCP Servers section)
   • .github/standards/ai-tooling-capabilities.md (MCP inventory)

Evaluating Git MCP Servers (§8.8.5 Backlog)

If agents need git history access (blame, log, diff), evaluate:

• @anthropic/mcp-server-git — Anthropic's official git MCP server
• GitKraken MCP (if installed) — mcp_gitkraken_* tools already available
• Before adding, verify: Does the agent need git history, or can it use run_in_terminal with git?

Verifying GitHub PAT Scopes

The github MCP server requires a PAT with these minimum scopes:

• repo — full repository access (read/write)
• workflow — GitHub Actions (trigger, read status)
• read:packages — package registry access

Verify with: gh auth status (check "Token scopes:" line).

Action Version Audit and SHA Pinning

Why SHA Pin?

Tag-based references like actions/checkout@v4 can be force-pushed. SHA pinning prevents supply-chain attacks where a compromised action replaces its tag.

Step-by-Step: Audit Action Versions

# List all action references across workflows (sorted unique)
Get-ChildItem .github/workflows/*.yml | ForEach-Object {
    Select-String -Path $_.FullName -Pattern 'uses:\s+(\S+)@(\S+)' | ForEach-Object {
        $_.Matches[0].Groups[1].Value + "@" + $_.Matches[0].Groups[2].Value
    }
} | Sort-Object -Unique

Step-by-Step: Pin Action to SHA

1. Find the action's release tag on GitHub: https://github.com/<owner>/<action>/releases
2. Find the commit SHA for that tag: git ls-remote https://github.com/<owner>/<action> refs/tags/v4
3. Replace tag reference with SHA + comment:

   # Before:
   - uses: actions/checkout@v4
   # After:
   - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683  # v4.2.2
   

4. The # vX.Y.Z comment is mandatory for readability.

Approved Action Registry

Renovate / Dependabot Auto-Update

If using Dependabot for github-actions ecosystem, it will auto-update SHA pins when a new release is published. Ensure .github/dependabot.yml includes:

- package-ecosystem: "github-actions"
  directory: "/"
  schedule:
    interval: "weekly"

Node.js 24 Migration Playbook

GitHub Actions is migrating from Node.js 20 to Node.js 24. Actions still using Node 16 or 20 will emit deprecation warnings and eventually fail.

How to Opt In

Add this env variable to every workflow's top-level env: block:

env:
  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true

Audit Procedure

1. Search all workflows for actions that may use old Node.js:

   Get-ChildItem .github/workflows/*.yml | ForEach-Object {
       Select-String -Path $_.FullName -Pattern 'uses:\s+\S+@' | ForEach-Object { $_.Line.Trim() }
   } | Sort-Object -Unique
   

2. Check each action's action.yml for runs.using: — should be node20 or node24.
3. Upgrade any action still at @v3 to @v4 (which targets Node 20+).
4. Set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true in every workflow.

ExplorerLens Status

All 22 workflows now set FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true (verified S101). All actions are at @v4 or later. No Node 16 actions remain.

Troubleshooting

AI Tooling Inventory (Current State)

Required Constraints

1. Never describe a workflow that does not exist in .github/workflows/.
2. Never document MCP servers absent from .vscode/mcp.json.
3. Always update ai-tooling-capabilities.md in the same commit as AI asset changes.
4. Never pin toolset: in ilammy/msvc-dev-cmd@v1 — breaks GitHub-hosted runners.
5. Corporate artifacts (intel.com, NO_PROXY, port 928) must never appear in tracked files.
6. Instructions must have correct applyTo: frontmatter — test that scoping works as intended.

Canonical File Paths

Validation Checklist

• Workflow names in markdown exactly match workflow filenames in .github/workflows/
• MCP server names and scopes match .vscode/mcp.json
• All instructions have applyTo: frontmatter
• All skills are ≥ 100 lines with step-by-step procedures
• ai-tooling-capabilities.md counts match actual file counts
• No stale references to retired conventions (.github/AGENTS.md, CODEOWNERS old casing)
• No corporate proxy URLs in any .vscode/ or .github/ file