What problem does it solve? When a pull request changes code, it is often unclear whether documentation must change too, and if so, which file should carry the update. This Skill resolves that triage by judging changes on reader-observable behavior rather than edit location, and by routing each update to the correct surface. ## Core Features & Use Cases - Documentation impact triage: Determines whether a change is user-observable and owes a doc update, treating "no update needed" as a legitimate outcome for refactors and test-only edits. - Surface routing: Assigns each update to exactly one owner — README.md for the tour and quick start, AGENTS.md for architecture and rules, CONTRIBUTING.md for setup and PR process, .env.example for environment variables, or TSDoc for published symbol contracts. - Skill lifecycle tracking: Records skill additions, renames, and deletions in AGENTS.md's Skills table, which a test asserts stays in sync with the authored directory. - Use Case: A pull request moves an architecture boundary between zones. Use this Skill to decide the change belongs in AGENTS.md, not README.md, and that no CONTRIBUTING.md edit is owed. ## Quick Start Ask the agent to review your pull request diff and decide which documentation files, if any, need to be updated.
