skills.rest
madhavmadupu
madhavmadupuCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Check Documentation Drift

Detect missing file references and orphaned documentation in a repository.

Updated Feb 10, 2026
Search Tags:#code review#documentation#technical writing#adr#repository management#code drift
One-click install
npx skills add https://github.com/madhavmadupu/atlas-mobile --skill check-documentation-drift
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Check Documentation Drift
Source: https://github.com/madhavmadupu/atlas-mobile/tree/main/.agent/skills/check-drift
Command: npx skills add https://github.com/madhavmadupu/atlas-mobile --skill check-documentation-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and helps resolve discrepancies between your project's documentation and its actual codebase, preventing outdated or inaccurate information from misleading developers and users.

Core Features & Use Cases

  • Detect Missing Files: Flags documentation that references files that do not exist in the repository.
  • Identify Orphaned Docs: Highlights documentation for modules or domains that have no corresponding code.
  • Verify "What's Built": Facilitates manual review of current-state.md against the codebase.
  • Check ADR Index: Compares the list of Architecture Decision Records (ADRs) in the index against the actual ADR files.

Quick Start

Run the check-drift skill to analyze the documentation against the current codebase.

Frequently Asked Questions about Check Documentation Drift

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

FAQPage Schema
How do I detect documentation drift in a code repository?▼

Documentation drift occurs when documentation artifacts lose sync with the codebase, referencing missing files or orphaned modules. Detecting it requires comparing docs against code to identify inconsistencies and verify built features.

How do I check for orphaned module documentation in my repository?▼

Checking for orphaned module documentation involves scanning the repository to highlight documentation for modules or domains that have no corresponding code. This flags outdated docs for removal or updates.

What is the best way to verify architecture decision record indexing against actual files?▼

Verifying architecture decision record indexing involves comparing the ADR index list against the actual ADR files in the repository. This flags missing or orphaned ADRs to ensure indexing consistency.

Can I verify what's built in a repository against the current-state documentation?▼

Yes, you can verify what's built by facilitating a manual review of the current-state.md file against the codebase. This checks that documented features match the actual implemented code.

Does documentation drift detection work without specific dependencies or external tools?▼

Documentation drift detection operates using internal scripts and references without requiring external dependencies. It analyzes the repository structure directly to report missing files and orphaned docs.

Related Skills

Explore More Software Engineering Skills→
tkstangtkstang

update-repo-reference

Synchronize repository reference documentation with current OAT implementation changes.

Community
Intermediate
LazyNinja435LazyNinja435
1

Dispatcher Maintenance

Validate and synchronize AstrAI dispatcher files across the .ai/ directory.

Community
Intermediate
jaballerjaballer
2

ftf-open-pr

Automates GitHub pull request creation for WordPress repositories using structured templates.

Community
Intermediate
channgchanng
20

docsify

Generate static documentation websites from markdown files with sidebar navigation.

Community
Basic