ship-milestone

Automate a milestone release by aggregating plan and spec data, applying version bumps, updating changelogs, and generating one reviewable commit. The skill prompts for human approval before committing, ensuring an auditable release flow without automatic pushes.

An atomic milestone release bundles version bumps, changelog updates, and documentation regeneration into a single auditable commit. Human approval gates the commit to prevent unreviewed changes, ensuring error-free manual coordination of specs and release docs.

Update changelogs and release docs by applying scripted transformations to four release files, including CLAUDE.md. The process reads milestone scope from plan files, regenerates documentation, and prompts for a codename and summary text before finalizing the commit.

Yes, the workflow runs locally without dependencies or CI components. It reads specs directly from your repository, applies version bumps, and pauses for human approval before generating a commit, making it suitable for local execution.

Coordinate spec files and documentation by aggregating plan data to determine milestone scope, then regenerating release docs and applying version bumps in one atomic commit. This ensures changelogs and CLAUDE.md updates stay synchronized with your spec requirements.

Documentation changes occur because the release process regenerates docs and updates CLAUDE.md alongside version bumps to maintain synchronization. This bundling is intentional, ensuring the single atomic commit reflects the complete milestone scope and all related artifacts.