Update core project docs after shipped code changes.
npx skills add https://github.com/stayconnectquick/gstack --skill document-release-stayconnectquick
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/stayconnectquick/gstack/tree/main/document-release Command: npx skills add https://github.com/stayconnectquick/gstack --skill document-release-stayconnectquick
Post-ship documentation often drifts as changes are shipped. This Skill reads project docs, cross-references diffs, and updates key files to keep READMEs, architecture notes, contributing guidelines, and CLAUDE notes in sync with what was released.
Invoke document-release after a ship to synchronize docs and update CHANGELOG.
High-intent search queries and answers about installing and using this skill.
You can automatically update README and CHANGELOG after a PR merge by invoking a post-ship documentation Skill that reads project docs, cross-references the shipped diff, and applies synchronized updates to reflect the released code changes.
Keeping architecture docs in sync relies on cross-referencing shipped diffs against existing documentation, then applying targeted edits to ARCHITECTURE.md and CLAUDE.md to accurately reflect the latest structural and behavioral modifications.
Cleaning up TODOs and polishing the CHANGELOG voice after shipping involves reading the post-merge diff, refining the changelog text for clarity, and removing resolved task markers to maintain accurate release documentation.
Yes, you can optionally bump the VERSION file alongside documentation updates after a release, using Bash, Read, Write, and Edit commands to ensure version tracking stays synchronized with shipped code changes.
Post-ship documentation synchronization specifically targets repositories containing README.md, ARCHITECTURE.md, CONTRIBUTING.md, CLAUDE.md, and CHANGELOG.md, so missing core files like CLAUDE.md limit the cross-doc synchronization scope.
Documentation drift after shipping code changes occurs because manual updates are often skipped during releases, creating misalignment that requires cross-referencing the shipped diff against project docs to proactively suggest and apply corrective edits.
ibalasiteAutomates post-ship documentation updates by reading project diffs and aligning docs.
Wilder1222Automate release coordination with version tagging, changelog generation, and GitHub publication.
dogearedAlign README.md, ARCHITECTURE.md, CONTRIBUTING.md, and CLAUDE.md with shipped code changes.
shekerkammaUpdate project documentation to match shipped code changes.
