skills.rest
trevorbyrum
trevorbyrumCOMMUNITY
Explore all skills by this author →
GitHub

drift-review

Compare project documentation files against the codebase to report discrepancies.

1|1|Updated Mar 9, 2026
Search Tags:#project management#code review#documentation#drift detection#codebase analysis#sync
One-click install
npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill drift-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: drift-review
Source: https://github.com/trevorbyrum/claude-skills-suite/tree/main/skills/drift-review
Command: npx skills add https://github.com/trevorbyrum/claude-skills-suite --skill drift-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires codex, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically detects and reports discrepancies between your project's documentation (like project-context.md, features.md, project-plan.md) and the actual codebase, ensuring that your documentation remains an accurate reflection of the project's reality.

Core Features & Use Cases

  • Code-to-Docs Verification: Identifies implemented features or architecture that are missing from documentation.
  • Docs-to-Code Verification: Flags documentation that describes features or architecture not present in the code.
  • Status Accuracy Check: Verifies if the completion status of features and plan phases in documentation aligns with the code's state.
  • Use Case: After a sprint, run this skill to confirm that all features marked as "done" in features.md are fully implemented in the code, and that no new, undocumented functionality has been introduced.

Quick Start

Check if the project documentation is out of sync with the codebase.

Frequently Asked Questions about drift-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect documentation drift in my codebase?▼

Documentation drift is detected by comparing project files like project-context.md, features.md, and project-plan.md against the actual codebase to identify and report discrepancies in architecture, features, and implementation status.

Can I check if my project documentation matches the implemented code?▼

You can verify documentation matches code by checking both directions: finding implemented features missing from docs, and flagging documentation that describes features or architecture not present in the codebase.

How do I verify feature completion status in my project plan?▼

Feature completion status verification checks if the completion status of features and plan phases documented in files like features.md aligns with the actual implementation state of the codebase.

Does this codebase analysis work with Codex to find undocumented features?▼

Codebase analysis works with Codex by utilizing code-side discovery to find undocumented elements, ensuring that newly implemented features or architecture missing from project documentation are identified.

What is the best way to sync project documentation after a sprint?▼

To sync project documentation after a sprint, run a drift detection check to confirm features marked as done are fully implemented and no undocumented functionality has been introduced into the codebase.

Related Skills

Explore More Software Engineering Skills→
cmbayscmbays
1

doc-sync

Detect and report drift between markdown documentation and source code.

Community
Advanced
JasonLoJasonLo

sync-docs

Audit documentation files against the codebase and correct discrepancies.

Community
Intermediate
mjamoremjamore

repo-docs

Synchronize repository documentation with source code using doc-first workflows.

Community
Advanced
andregusman-raizandregusman-raiz
19

ag-validar-execucao

Validate plan items against the codebase and report done, partial, and missing totals.

Community
Advanced