doc-drift-en

Compare documentation claims against implementation code and generate drift reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ensures that your documentation accurately reflects your implementation code, preventing outdated information and inconsistencies.

Core Features & Use Cases

  • Drift Detection: Compares claims made in documentation against actual code.
  • Report Generation: Creates detailed reports highlighting discrepancies.
  • Use Case: After updating a feature, run this Skill to verify that the README.md and API documentation still accurately describe the new functionality and its parameters.

Quick Start

Use the doc-drift-en skill to check for documentation drift in the current project.

Frequently Asked Questions about doc-drift-en

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

FAQPage Schema
How do I check for documentation drift in my codebase?

This Skill detects documentation drift by cross-referencing claims in your docs against actual implementation code, generating detailed reports that highlight discrepancies and outdated information for software development projects.

What is documentation drift detection and when do I need it?

Documentation drift detection identifies inconsistencies between your README or API docs and your implementation code. You need it after updating features to verify your documentation accurately describes the new functionality and its parameters.

How do I verify my README and API docs match my updated code?

You can verify your README and API docs by running this Skill to compare documentation claims against the updated implementation code, which then produces a drift report highlighting any mismatches that need fixing.

Do I need GitHub CLI to generate code consistency reports?

Yes, you need the GitHub CLI installed, as this Skill requires it for issue reporting and for adhering to specific document discovery and cross-referencing criteria during drift detection.

Does documentation drift detection work with GitHub issue reporting?

Yes, this Skill integrates with GitHub issue reporting through the GitHub CLI, allowing you to document discovered code-to-spec alignment inconsistencies directly within your repository workflow.