skills.rest
highflame-ai
highflame-aiOFFICIAL
Explore all skills by this author →
Website𝕏@javelinaiGitHub

doc-drift

Extract public surface changes from git diffs to audit documentation drift.

4|Updated Jul 20, 2026
Search Tags:#automation#git#documentation#maintenance#drift#code-sync
One-click install
npx skills add https://github.com/highflame-ai/ai-factory --skill doc-drift-highflame-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doc-drift
Source: https://github.com/highflame-ai/ai-factory/tree/main/skills/doc-drift
Command: npx skills add https://github.com/highflame-ai/ai-factory --skill doc-drift-highflame-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of documentation rot, where technical documentation becomes stale or inaccurate following code changes, leading to developer confusion and integration errors.

Core Features & Use Cases

  • Surface Analysis: Automatically identifies changed public surfaces like API routes, CLI flags, and config keys from git diffs.
  • Drift Detection: Scans documentation files to classify mentions as stale, missing, or historical.
  • Automated Remediation: Provides targeted updates to keep docs honest and accurate relative to the current codebase.

Quick Start

Run the doc-drift skill by providing the relevant commit range or PR number to identify and fix stale documentation references.

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 after code changes in a git repository?▼

Documentation drift is detected by extracting public surface changes like API routes and CLI flags from git diffs and auditing project documentation to classify mentions as stale, missing, or historical.

How do I keep API specifications and CLI docs synced with my codebase?▼

Keeping API specifications and CLI docs synced involves cross-file impact analysis on git diffs to identify changed public surfaces and apply targeted automated remediation to external-facing guides.

What is the best way to automate fixing stale documentation references?▼

Automating stale documentation fixes requires analyzing commit ranges or PR numbers to identify changed configuration files and CLI flags, then applying targeted updates to ensure parity with the codebase.

Do I need specific tools to perform cross-file documentation analysis?▼

Cross-file documentation analysis requires git and standard unix text processing utilities to perform verification across API specifications, CLI documentation, and configuration files.

Can I audit configuration file documentation against implementation changes?▼

Auditing configuration file documentation is supported by extracting changed configuration keys from git diffs and verifying parity between implementation details and external-facing guides.

When should I avoid using doc-drift for documentation maintenance?▼

Documentation maintenance via doc-drift may not suit projects lacking git version control or standard unix text processing utilities, as cross-file impact analysis and verification depend on these tools.

Related Skills

Explore More Software Engineering Skills→
maxenkomaxenko
1

code-scrutiny

Review recent code changes to surface bugs and refactoring opportunities.

Community
Advanced
phrazzldphrazzld
13

github-cli-hygiene

Write GitHub CLI pull requests, issues, and reviews via body files with post-write validation.

Community
Intermediate
roycolumbia-coderoycolumbia-code

gsd-ship

Automates GitHub pull request creation, review triggering, and merge tracking.

Community
Intermediate
channgchanng
20

docsify

Generate static documentation websites from markdown files with sidebar navigation.

Community
Basic