document-drift

Audits repository documentation against codebase to detect and report drift.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/doolin/dave-skills --skill document-drift
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-drift
Source: https://github.com/doolin/dave-skills/tree/main/skills/document-drift
Command: npx skills add https://github.com/doolin/dave-skills --skill document-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically find and fix places where documentation has fallen out of sync with the code it describes.

Core Features & Use Cases

  • Surface broken cross-references, outdated lists, and orphaned mentions across top-level docs like SKILL.md, AGENTS.md, README.md, and docs/**.
  • Validate the consistency between docs and the codebase, and generate a reconciled report with suggested fixes.
  • Use case: run a quarterly drift audit across a repository to keep docs aligned with features and APIs.

Quick Start

Run the audit on your repository to produce a drift report and optional fixes.

Frequently Asked Questions about document-drift

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

FAQPage Schema
How do I audit documentation for drift against a codebase?

To audit documentation drift, this Skill inventories top-level files like README.md, AGENTS.md, and docs/, verifies cross-references against the codebase, and generates a deterministic drift report with optional fixes.

What causes stale content and broken cross-references in repository docs?

Stale content and broken cross-references occur when code changes outpace updates to files like SKILL.md or README.md, leaving outdated lists and orphaned mentions that a drift audit surfaces and reconciles.

Can I use this to validate references in top-level docs like AGENTS.md and SKILL.md?

Yes, you can validate references in top-level docs like AGENTS.md and SKILL.md by running the audit, which performs inventory and cross-reference checks to detect drift and produce a reconciled report.

What is the best way to run a quarterly documentation compliance audit?

The best way to run a quarterly documentation compliance audit is applying this deterministic process to inventory docs, verify references, and output a drift report with suggested fixes to keep docs aligned.

How do I fix orphaned mentions and outdated lists in markdown documentation?

To fix orphaned mentions and outdated lists in markdown documentation, the audit produces a drift report that identifies these inconsistencies and provides optional fixes to reconcile the content.

Does this documentation audit work on the docs directory or only root-level files?

This documentation audit works on both root-level files like README.md and the docs/ directory, performing inventory and cross-reference checks across all specified locations to detect drift and stale content.