Analyze git diff to identify code changes requiring documentation updates. Categorizes changes (database/schema, API endpoints, components, configuration, authentication) and suggests relevant documentation files to review. Use when: (1) After making code changes, (2) Before committing significant changes, (3) When adding new features or modifying APIs, (4) During PR preparation, (5) When working with database schemas, API routes, components, or configuration files, (6) To ensure documentation …
Analyze git diff to identify code changes requiring documentation updates.
Categorizes changes (database/schema, API endpoints, components, configuration, authentication) and suggests relevant documentation files to review.
Use when: (1) After making code changes, (2) Before committing significant changes, (3) When adding new features or modifying APIs, (4) During PR preparation, (5) When working with database schemas, API routes, components, or configuration files, (6) To ensure documentation stays synchronized with code changes, (7) For documentation sync and maintenance, or (8) For pre-commit documentation checks.
Triggers: check docs, docs check, documentation check, update docs, sync documentation, what docs need updating, check if docs are up to date, after code changes, before committing.
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
REQUIRED READING: Always load references/documentation-guide.md to:
Validate existing documentation - Check if suggested docs follow correct structure, style, and alignment
Guide updates - Reference standards when writing or updating documentation
The guide contains all standards, examples, patterns, and requirements. Do not make assumptions about documentation format, style, or structure - always reference the guide.
Documentation Guide: references/documentation-guide.md - REQUIRED: Complete documentation standards, style, structure, and examples. Load this file to validate existing docs and guide updates.
docs-write skill: skills/docs-write/SKILL.md - Complete workflow for writing/updating documentation
Output
The tool outputs:
Changed code files organized by category
Suggested documentation files to review
Guidance on what needs to be updated
Best Practices
Run this check before committing significant changes
Always load references/documentation-guide.md to validate documentation structure and alignment
Verify existing documentation follows guide standards (style, structure, format) - not just detect what needs updating
Review the [Documentation Guide](references/documentation-guide.md) to understand what changes require documentation
Update documentation in the same PR as code changes
Fix structure/alignment issues when updating content
Use the verbose mode for more detailed information
