Analyze git changes to detect documentation drift and generate a findings report.
npx skills add https://github.com/kvet/queuert --skill docs-check-kvet
Please help me install this Agent Skill. Skill: docs-check Source: https://github.com/kvet/queuert/tree/main/.claude/skills/docs-check Command: npx skills add https://github.com/kvet/queuert --skill docs-check-kvet
Documentation often drifts from the codebase as development progresses. This skill helps teams automatically identify documentation that needs updating by analyzing git changes and comparing them against design docs, package READMEs, and CLAUDE.md.
Run the docs-check tool to analyze current changes and produce a report.
/docs-check /docs-check --staged /docs-check <commit> /docs-check <base>..<head>
High-intent search queries and answers about installing and using this skill.
To detect documentation drift, you can analyze git changes to map code modifications against design docs, package READMEs, and CLAUDE.md, generating a structured findings report highlighting specific files and sections that need updating.
Keeping package READMEs and design docs in sync involves analyzing git diffs to categorize impact and map changes to relevant documentation sections, then delivering a structured report for action.
Yes, you can check staged changes or specific commits by passing arguments like --staged, a specific commit hash, or a base..head range to analyze those exact git changes for documentation drift.
Yes, documentation drift detection works without external dependencies, directly analyzing your git history and file structure to map code changes to relevant documentation sections.
You need to run a documentation audit during release workflows, design review cycles, or ongoing documentation hygiene maintenance to ensure design docs, package READMEs, and CLAUDE.md accurately reflect current code changes.
Mapping code changes to documentation sections works by analyzing git diffs, categorizing the impact of those code modifications, and matching them to relevant sections within design docs, package READMEs, and CLAUDE.md files.
ousiassAnalyze Git diffs for code quality and documentation drift.
ShaheerKhawajaSync shipped code changes with project documentation to correct drift.
686f6c61Analyzes Git diffs and executes relevant unit, integration and E2E tests to detect regressions.
kvetAnalyze git changes to detect documentation drift and generate a findings report.
