audit-docs

Documentation drift is detected by auditing user-facing docs like README.md and AGENTS.md to validate settings names, defaults, command IDs, file paths, and tool names against current code. Patches are written directly to the working tree for review.

Auditing contributor guides involves validating references like settings names, command palette IDs, and tool names against the codebase. This skill compares docs/guide/ and docs/reference/ files to the code and patches inconsistencies in the working tree.

Yes, you can patch README.md and AGENTS.md files by auditing them against the codebase. The skill identifies drift in settings, defaults, and paths, then applies minimal patches directly to the working tree for you to commit.

No additional dependencies are required to validate documentation against code. The skill operates independently to compare user-facing docs with the codebase and write drift patches to the working tree without external tools.

To verify settings names and defaults, audit docs/reference/ files against the codebase. The skill checks for drift in configuration values, command palette IDs, and file paths, patching discrepancies directly in the working tree.

Patching documentation drift in the working tree does not automatically commit changes or open pull requests. The caller remains responsible for reviewing diffs, committing patched files, and opening PRs to merge the validated documentation.