Detect documentation and implementation drift across repository files.
npx skills add https://github.com/jmagar/rust-bin --skill check-project-drift
Please help me install this Agent Skill. Skill: check-project-drift Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/check-project-drift Command: npx skills add https://github.com/jmagar/rust-bin --skill check-project-drift
Drift between documentation and code undermines trust, slows onboarding, and increases maintenance risk. This skill centralizes checks that surface inconsistencies across knowledge maps, spec.md vs xtask parity, exec-plan lifecycles, stale active plans, and ADR coverage, enabling teams to act with context.
Run the drift checks against the repository and review the resulting report.
High-intent search queries and answers about installing and using this skill.
You can detect documentation drift by running deterministic checks across your repository that compare knowledge maps, spec.md versus xtask parity, exec-plan lifecycles, and ADR coverage. The skill produces a structured report surfacing inconsistencies without requiring code changes.
Spec.md versus xtask parity checking verifies that implemented commands and execution plans documented in spec.md actually exist and reflect the current codebase. It surfaces inconsistencies between documented specifications and actual implementation behavior.
Yes, ADR coverage and stale active plan checks are designed to surface inconsistencies during development and code reviews. Running these deterministic checks before major releases helps identify missing or outdated architectural decision records.
The best way to verify knowledge-map integrity is running automated drift checks that scan repository files for alignment. This centralizes consistency verification and produces a structured report highlighting gaps and misalignments.
Drift reporting requires no code changes to the repository. It enforces deterministic checks against existing files and outputs a structured report identifying inconsistencies, enabling teams to act with context.
SteveGJonesCompare knowledge base shelf-index hashes against library files to detect drift.
githubQuery live Microsoft 365 emails, meetings, documents, Teams messages, and people data.
s3nex-comVerify service implementations against OpenAPI specs using Pact or Schema Registry.
nikhillinitDetect code and documentation drift and validate embedded examples.
