ワンクリックで
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 ページを確認してインストールできます。
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
SOC 職業分類に基づく
| 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).