Menü
Audit VS Code extensions against the current project stack and recommend keep/add/remove actions
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Health check procedures D1–D14 for the Audit agent — structural validation, attention budget, version checks, workspace integrity, and static audit
Configure and manage Model Context Protocol servers for external tool access
Review a UI for accessibility — WCAG 2.1 AA compliance, semantic HTML, ARIA usage, keyboard navigation, focus management, colour contrast, and screen reader compatibility
Design or review a REST or GraphQL API — resource modeling, versioning strategy, error contract, OpenAPI/schema-first workflow, and security baseline
Generate a CHANGELOG.md entry from staged changes, a commit range, or a PR diff — following Keep a Changelog format with conventional commit classification
Set up and audit environment variable management — create .env.example, add startup validation, separate secrets from config, and document every variable
| name | extension-review |
| description | Audit VS Code extensions against the current project stack and recommend keep/add/remove actions |
| compatibility | >=3.2 |
Skill metadata: version "1.1"; license MIT; tags [extensions, vscode, audit, tooling, review, plugins]; compatibility ">=3.2"; recommended tools [codebase, fetch, runCommands].
Review the current project's VS Code extensions and recommend what to keep, add, or remove based on the actual stack in the repository.
.vscode/extensions.json directly without auditGet the installed list - Try to enumerate extensions automatically using the runCommands tool:
code --list-extensions --show-versions | sort
If the command fails (e.g., code CLI not on PATH or terminal unavailable), fall back to asking the user to run code --list-extensions | sort and paste the output.
Profile check — Detect repo-specific VS Code Profile. If on Default Profile, recommend creating a dedicated Empty Profile. If profile detection is limited, note it and recommend repo-specific profile.
Read workspace recommendations — Inspect .vscode/extensions.json and .vscode/settings.json.
Detect the stack — Scan repo for language, runtime, linter, formatter, test, and config signals.
Audit agent plugins — @agentPlugins in Extensions view. Check for overlap with extensions, MCP server duplication, and stack relevance.
Check MCP-contributing extensions — Cross-reference .vscode/mcp.json with extension-contributed servers for duplicates.
Compare installed vs needed — Build: Keep (relevant), Recommended additions (needed for stack), Consider removing (irrelevant/duplicate/deprecated).
Unknown stacks — Research Marketplace; only recommend if installs >100k, rating ≥4.0, updated within 12 months.
Persist new mappings — Append to .copilot/workspace/knowledge/TOOLS.md under Extension registry.
Present the report - Use this structure:
## Extension Review - <project>
### Keep
- `publisher.extension` - why it still fits
### Recommended additions
- `publisher.extension` - what it provides | why needed
Install: Ctrl+P -> `ext install publisher.extension`
### Consider removing
- `publisher.extension` - duplicate / unused language / deprecated
### Agent plugins
- `plugin-name` - keep / remove / overlaps with `publisher.extension`
### Notes
- stack signals discovered
- unknown stacks researched
- extension registry updates made
- MCP server overlaps identified
Wait - Do not modify .vscode/extensions.json or install/uninstall anything until the user explicitly asks.