원클릭으로
vscode-extension-doc-audit
How to audit VS Code extension docs against package.json for accuracy
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
How to audit VS Code extension docs against package.json for accuracy
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Casey's preferred workflow patterns for PRs, planning, git worktrees, ADO integration, and team communication
How to start working on an EditLess issue: worktree creation, isolated VS Code, branch conventions
| name | vscode-extension-doc-audit |
| description | How to audit VS Code extension docs against package.json for accuracy |
| domain | documentation |
| confidence | low |
| source | earned |
VS Code extensions define their public API in package.json under contributes. Documentation (settings references, command lists, keybinding guides) must match this source of truth exactly. Drift happens frequently because package.json changes don't automatically propagate to docs.
contributes.configuration)For each setting in package.json, verify in docs:
resource, window, machine, etc. must match exactly. "resource" ≠ "workspace".string, number, boolean, array, object.markdownDescription is the rich version; keep docs consistent with it.contributes.commands)commandPalette when: "false" entries — these are context-only commands, not discoverable from palette.contributes.keybindings)key) and macOS (mac) variants in docs.Always treat package.json as the single source of truth. When docs and code disagree, update docs to match code (not the other way around).