update-docs

You can automatically sync documentation with code changes by analyzing commit ranges or the working tree to route updates to README, AGENTS.md, CHANGELOG, and docs/ files. This Skill supports post-commit hook automation to keep project docs aligned.

To keep your README and CHANGELOG updated after a git commit, trigger the post-commit hook for automatic routing or manually run /update-docs HEAD~3..HEAD to analyze recent commits and apply changes to the appropriate documentation files.

Yes, you can update docs from uncommitted changes by using the manual working tree mode. Running /update-docs --working-tree analyzes your current uncommitted modifications and routes the necessary updates to your project documentation.

The README-as-landing-page pattern enforces keeping your README file as a high-level entry point with links to detailed docs. This Skill automatically routes granular updates to the docs/ directory while maintaining this structural pattern.

You can audit project documentation for missing updates by running /update-docs --audit. This mode reviews your current codebase and documentation state to identify where docs are out of sync with recent changes.

No, this documentation sync tool does not require any external dependencies. It operates independently to analyze git commit ranges and working tree changes to route updates across your README, AGENTS.md, CHANGELOG, and docs/ files.