doc-drift

Detect and report documentation and implementation code discrepancies.

Updated Feb 9, 2026
One-click install
npx skills add https://github.com/ousiass/claude-config --skill doc-drift
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: doc-drift
Source: https://github.com/ousiass/claude-config/tree/main/skills/doc-drift
Command: npx skills add https://github.com/ousiass/claude-config --skill doc-drift

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automatically detects and reports discrepancies between your documentation and your codebase, ensuring your documentation remains an accurate source of truth.

Core Features & Use Cases

  • Automated Drift Detection: Compares documentation content (APIs, configurations, features) against actual code implementation.
  • Prioritized Reporting: Assigns severity levels (πŸ”΄πŸŸ πŸŸ‘πŸŸ’) to detected discrepancies.
  • Use Case: After updating an API endpoint, run this Skill to verify that the README.md and API documentation accurately reflect the new function signature, parameters, and expected behavior.

Quick Start

Run the doc-drift skill to check for inconsistencies between documentation and code in the current project.

Frequently Asked Questions about doc-drift

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

FAQPage Schema
How do I detect documentation drift between my API documentation and implementation code?β–Ό

To detect documentation drift, the Skill compares documentation content against actual code implementation to identify mismatches in API interfaces, data models, and configurations. It assigns severity levels to detected discrepancies for prioritized reporting.

What is the best way to keep code and docs in sync after updating an API endpoint?β–Ό

The best way to keep code and docs in sync is running an automated drift detection check after implementation changes. This verifies that README and API documentation accurately reflect new function signatures, parameters, and expected behaviors.

Do I need the GitHub CLI to report documentation discrepancies?β–Ό

Yes, the GitHub CLI (`gh`) is required for reporting documentation discrepancies. It enables the automated creation of GitHub Issues to track detected mismatches between your technical writing and codebase.

How does severity assessment work for documentation and code mismatches?β–Ό

Severity assessment for documentation drift relies on defined check criteria to evaluate discrepancies across configurations and features. Detected mismatches are then categorized into prioritized severity levels to streamline remediation.

Can I check for configuration drift in my technical writing without setting up dependencies?β–Ό

Checking configuration drift requires no external dependencies, but you must define check criteria to assess severity accurately. The Skill operates directly on your project to compare configurations against technical writing.