Automates post-ship documentation updates by reading project diffs and aligning docs.
npx skills add https://github.com/ibalasite/gstack --skill document-release-ibalasite
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/ibalasite/gstack/tree/main/document-release Command: npx skills add https://github.com/ibalasite/gstack --skill document-release-ibalasite
Post-ship documentation frequently drifts after code changes. This skill automates the process to read diffs and align multiple docs with what shipped, reducing manual toil and drift.
Run document-release after shipping to automatically refresh and align documentation across the project.
High-intent search queries and answers about installing and using this skill.
Automating post-ship documentation updates involves reading project diffs, cross-referencing affected files, and aligning docs with what shipped. This process automatically refreshes README, ARCHITECTURE, CONTRIBUTING, and CHANGELOG files to reflect merged changes.
Syncing CHANGELOG entries with merged PRs is done by analyzing project diffs and polishing the language to match the shipped code. The process cleans up TODOS and aligns the documentation with the actual modifications introduced in the merge.
Keeping README and ARCHITECTURE docs aligned with code changes requires cross-referencing project diffs against these files. This ensures the documentation accurately reflects the shipped features and structural updates without manual toil.
Automatically bumping the version during post-ship documentation updates is supported. When requested, the workflow reads the project diff, aligns the core documentation, and optionally increments the project VERSION file to match the new release state.
Post-ship docs sync operates without external dependencies, relying on the gstack environment configuration. It supports optional proactive suggestions and contributor mode to tailor the documentation updates directly within the project workflow.
jayteealaoSynchronize version numbers across project files and documentation references.
tyhuffman7Align project documentation with shipped changes by reading diffs.
diiviikk5Sync post-ship diffs across README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md.
GrassHopper42Automates documentation updates after release using Git diff analysis and Markdown files.
