docs-consistency

Align documentation files with codebase changes to prevent drift.

88|4|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/uhyo/funstack-static --skill docs-consistency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-consistency
Source: https://github.com/uhyo/funstack-static/tree/main/.claude/skills/docs-consistency
Command: npx skills add https://github.com/uhyo/funstack-static --skill docs-consistency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Documentation files (packages/docs) should be consistent and up-to-date with the codebase. When you make changes to the codebase that affect documented features, or when you update documentation files, ensure that all relevant documentation files reflect the changes accurately.

Core Features & Use Cases

  • Automatic alignment of documentation with code changes after feature work or refactors.
  • Validation of updated features documentation and index pages to maintain navigability.
  • Use Case: After introducing a new feature or modifying an existing one, run the consistency check to update docs accordingly.

Quick Start

Run the docs-consistency check after any code or documentation change to ensure all docs stay aligned with the codebase.

Frequently Asked Questions about docs-consistency

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

FAQPage Schema
How do I keep documentation consistent with my codebase after refactoring?

To maintain documentation consistency after refactoring, run an automated alignment check that validates updated feature documentation against code changes to prevent drift and ensure all docs accurately reflect the codebase.

What causes documentation drift and how do I check for missing links?

Documentation drift occurs when codebase modifications are not reflected in docs. A consistency check identifies outdated sections and missing links by validating that all documentation files accurately mirror current feature implementations.

When should I run a documentation review for feature updates?

Run a documentation review whenever new features are introduced or existing ones are modified. This ensures updated feature documentation and index pages maintain navigability and accurately reflect the current codebase.

Does automated documentation review work without external dependencies?

Yes, automated documentation review can operate without external dependencies. The consistency check runs directly against your codebase and documentation files to validate alignment and detect outdated sections.

What is the best way to update index pages and feature documentation?

The best way to update feature documentation is applying an automated consistency check after code changes. This validates navigability by checking for missing links and outdated sections across all relevant documentation files.

Why are my documentation files showing outdated sections after code changes?

Outdated sections appear when documentation files are not updated alongside codebase changes. Running a consistency check detects these discrepancies by enforcing that all relevant docs reflect the modified features accurately.