documentation-consistency-keeper

Synchronize project documentation after spec or code changes.

1|Updated Jan 22, 2026

Search Tags:#automation #documentation #consistency #readability #references #change-tracking

Ready to run

npx skills add https://github.com/hohai99/antigravity-skills --skill documentation-consistency-keeper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: documentation-consistency-keeper
Source: https://github.com/hohai99/antigravity-skills/tree/main/.agent/skills/documentation-consistency-keeper
Command: npx skills add https://github.com/hohai99/antigravity-skills --skill documentation-consistency-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps all project documentation synchronized after spec or code changes. Outdated documentation becomes technical debt that causes confusion and errors.

Core Features & Use Cases

Dependent Document Mapping: Identify all documents affected by a change (e.g., README.md, docs/api.md, CHANGELOG.md).
Terminology Updates: Propagate terminology changes across multiple files to ensure consistency.
Outdated Content Removal: Remove statements that no longer apply and flag obsolete references.
Change Summary Generation: Produce a concise summary of what changed and where.
Use Case: After a spec update, run the keeper to align docs across README.md, API docs, and CHANGELOG.

Quick Start

Run the Documentation Consistency Keeper after any approved update to synchronize docs throughout the repository.

Frequently Asked Questions about documentation-consistency-keeper

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

FAQPage Schema

How do I keep project documentation synchronized after code or spec changes?▼

To keep project documentation synchronized after code or spec changes, you map dependent documents like README.md and API docs, propagate terminology updates, remove outdated statements, and generate a change summary.

What is the best way to update README and changelog files after modifying an API?▼

Updating README and changelog files after modifying an API involves mapping dependent documents, propagating terminology changes across files, removing obsolete references, and validating the updated content.

When do I need to run documentation consistency checks across a repository?▼

You need to run documentation consistency checks across a repository immediately after any approved spec or code update to prevent outdated documentation from causing technical debt and errors.

How does dependent document mapping work for technical documentation updates?▼

Dependent document mapping for technical documentation updates works by identifying all files affected by a change, such as README.md, docs/api.md, and CHANGELOG.md, ensuring every related reference is validated.

Can I automate change summary generation for multiple markdown files?▼

Yes, you can automate change summary generation for multiple markdown files by running a post-change workflow that maps dependencies, updates terminology, and produces a concise summary of what changed and where.

Why does outdated documentation cause technical debt in software projects?▼

Outdated documentation causes technical debt in software projects because unmapped changes leave obsolete references and outdated statements in files, which leads to developer confusion and integration errors.