Align project documentation with shipped changes by analyzing diffs.
npx skills add https://github.com/shaneholloman/ship --skill document-release-shaneholloman
Please help me install this Agent Skill. Skill: document-release Source: https://github.com/shaneholloman/ship/tree/main/document-release Command: npx skills add https://github.com/shaneholloman/ship --skill document-release-shaneholloman
Post-ship projects often drift where documentation no longer reflects shipped changes. This Skill ensures README, ARCHITECTURE, CONTRIBUTING, ARIA.md, and related docs stay accurate and consistent after a release.
Run the document-release workflow to update all project documentation to reflect shipped changes.
High-intent search queries and answers about installing and using this skill.
Keep documentation in sync by analyzing release diffs and cross-referencing files like README, ARCHITECTURE, and CONTRIBUTING to apply accurate, auditable post-ship edits automatically.
The best way to update README and CHANGELOG after a release is to cross-reference shipped diffs against existing docs, polish the CHANGELOG language, and clean up TODOS to reflect the final project state.
Yes, you can automatically bump package.json versions during the documentation update workflow when the analyzed shipped changes warrant a new release.
Yes, the docs-sync process supports ARIA.md and architecture files by cross-referencing shipped diffs against these files to ensure all project documentation remains accurate and consistent.
To ensure post-ship documentation edits are safe and auditable, use a workflow that analyzes diffs and applies structured updates to README, TODOS, and other docs while tracking all changes.
You need to cross-reference diffs to update project documentation when post-ship projects drift, ensuring that README, ARCHITECTURE, and CONTRIBUTING files accurately reflect the newly shipped code changes.
mgher668Synchronize README, ARCHITECTURE, CONTRIBUTING, and CLAUDE.md with shipped diffs.
AndrewDrygaCreate semantic version tags from changelogs and push them to Git.
bordenetValidate and verify Markdown links in documentation before publishing.
JEO-tech-aiGenerate OpenAPI/Swagger-compatible API documentation from definitions, schemas, and annotations.
