update-docs-and-commit

To keep documentation aligned with code changes, this Skill analyzes your diffs to identify user-visible updates and applies them directly to your CHANGELOG.md and README.md files. It then prepares a focused, well-annotated commit containing only the modified documentation.

The best way to keep a CHANGELOG updated with git commits is to analyze your code diffs for features, fixes, and deprecations, then generate a focused commit that captures these changes in your CHANGELOG.md. This reduces drift between code and docs.

To prepare a clean git commit that only includes updated docs, this Skill separates documentation updates from code changes and generates a focused commit message. It ensures your commits are well-annotated and contain only files like README.md and CHANGELOG.md.

Yes, you can use this to update README.md based on feature deprecations. The Skill specifically identifies user-visible changes such as deprecations from your code diffs and updates the relevant sections of your user-facing documentation accordingly.

You should avoid combining documentation updates with code changes when you need focused, well-annotated git history. This Skill isolates updated docs into a separate commit to maintain documentation quality and prevent unnecessary mixed changes.