Sync post-ship diffs across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md.
npx skills add https://github.com/diiviikk5/rezops --skill document-release-diiviikk5
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/diiviikk5/rezops/tree/main/document-release Command: npx skills add https://github.com/diiviikk5/rezops --skill document-release-diiviikk5
This Skill reduces manual post-release doc maintenance by automatically syncing shipped changes across key project docs and polishing language.
Run the document-release skill to update project docs after shipping.
High-intent search queries and answers about installing and using this skill.
To update project documentation after shipping, you can trigger a post-ship sync that cross-references diffs to align README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md with the latest changes.
Keeping a CHANGELOG and CLAUDE.md synced is done by cross-referencing shipped diffs, polishing CHANGELOG language, cleaning up TODOS, and optionally bumping the VERSION across project docs.
Yes, you can automatically clean up TODOS and optionally bump VERSION by running a post-ship documentation sync triggered after PR merges or code ships.
Updating README and ARCHITECTURE docs does not require manual diff checking; the process automatically cross-references shipped changes and syncs the documentation accordingly.
You need to sync documentation across multiple project files whenever you ship code, ensuring README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md reflect the latest shipped changes.
Automating post-ship docs updates requires access to the repository's existing documentation files and operates on post-ship contexts, meaning it cannot update docs without prior repo access.
ScivorUpdate and reconcile project documentation by cross-referencing diffs after a ship.
nesihaver-ILUpdate README, API, architecture docs, and changelogs after code changes.
vince-winkintelManage GitLab merge requests for creation, review, approval, and merging.
ajsai47Update project markdown documentation by cross-referencing git diffs after code commits.
