Update project docs to reflect shipped changes after PR merges.
npx skills add https://github.com/whd4/gstack --skill document-release-whd4
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/whd4/gstack/tree/main/document-release Command: npx skills add https://github.com/whd4/gstack --skill document-release-whd4
Post-ship documentation drift: teams ship features without aligning docs, which leads to stale README files, outdated ARCHITECTURE notes, diverging CONTRIBUTING guidelines, and unclear CLAUDE.md instructions. This skill automates cross-referencing shipped changes against project docs to keep core docs consistent and up-to-date.
After a PR is merged, run the document-release skill to synchronize docs with shipped changes.
High-intent search queries and answers about installing and using this skill.
To automatically update README and ARCHITECTURE docs after a PR merge, run the document-release skill to cross-reference shipped diffs and apply deterministic edits to mirror the changes across your project files.
Keeping documentation aligned with shipped code changes involves cross-referencing project diffs against existing docs to prevent documentation drift, ensuring README, ARCHITECTURE, and CONTRIBUTING files accurately reflect the latest features.
Yes, you can automatically polish the CHANGELOG and clean up TODOS when shipping a new version by running the document-release skill, which refines the changelog voice and optionally bumps the repository VERSION.
To prevent CLAUDE.md instructions from diverging after merging new features, automate post-ship documentation alignment by loading diffs into context and applying deterministic edits to keep instructions consistent.
Yes, the documentation update process works for any repository with a VERSION file, using Bash, Read, Write, and Grep commands to load changes into context and optionally bump the version across the repository after shipping.
You should use an automated post-ship documentation tool instead of manual edits when teams frequently ship features without aligning docs, leading to stale README files, outdated ARCHITECTURE notes, and diverging CONTRIBUTING guidelines.
tblakex01Update project documentation files to reflect shipped changes after PR merges.
nhattran998Cross-reference repository diffs and update project documentation after releases.
shaythegay13Automate the ship workflow by merging base branches, running tests, and creating pull requests.
nesihaver-ILUpdate README, API, architecture docs, and changelogs after code changes.
