概要
The Maintaining Docs After Changes skill prevents documentation drift by establishing a systematic approach to updating project documentation immediately following code modifications. It guides Claude through a rigorous two-phase process: first analyzing git diffs to identify specific documentation gaps, then updating content across READMEs, CLAUDE.md files, and specialized documentation directories. By enforcing the principle that documentation updates are non-optional components of a code change, this skill ensures that usage examples, troubleshooting guides, and implementation patterns remain accurate, reducing technical debt and onboarding friction.
