Release checklist for a Claude Code project For developers who release software with Claude Code or another coding assistant and want test evidence and a confirmation before anything is published. Steps 9
Checklist items 22
Language English
What it is for
Ship a release with your coding assistant: tests run on the release commit and loop until they are green, the tag is checked against that commit, and nothing is published without your yes.
For developers who release software with Claude Code or another coding assistant and want test evidence and a confirmation before anything is published.
Steps and what they prove 9
What ships The last release tag and the number of commits since it are quoted from the git output Breaking changes are listed with the commit that causes each, or the words none found The user agreed the new version number in this chat `git status` shows a clean tree, or the user said which uncommitted changes belong in the release Changelog, version and release commit The changelog diff is shown and every user-visible change from the scope step has a line `git grep` for the old version string returns nothing outside the changelog history The release commit id is quoted from `git rev-parse HEAD` Build and tests on the release commit The command, the commit id it ran on and the passed, failed and skipped counts are quoted from the output Every failing test is named with the first line of its error, or the words no failures The context variable testsGreen is set to the result (true or false) Fix the failing tests Each failing test has a cause written in one sentence and the commit that fixes it is quoted The failing test was run alone and its pass line is quoted testRound was raised by one and testsGreen was set to false Tag the release commit `git rev-parse <tag>^{commit}` is quoted and equals the commit id in the green test summary The tag has not been pushed (`git ls-remote --tags` does not list it) Confirm the publish with the user The summary screen was shown with the version, test counts, tag commit and exact publish commands The user's answer is quoted word for word in the step summary userConfirmed is true only after that yes Publish The output of each publish command is quoted in the step summary The release page or the registry page for the new version is named and opens Verify the release from a clean setup The release was installed from the published source on a clean setup and the version it reports is quoted Stop the release and report The report names the last test result with its counts, the commit and tag, and says that nothing was published The assistant closes a checklist item only with evidence of what it did, so a finished run shows the work was done, not only claimed.
Use it
Create a free account, connect your assistant and run this workflow in a chat. You come back to this page after signing up.
Use this template
Not sure yet? Watch a demo run first, no account needed.
Already have an account? Sign in