Pathista

Claude Code release checklist: example workflow - Pathista help center

Help pages: Release checklist for Claude Code

Updated

A release checklist for Claude Code works best when publishing sits behind recorded evidence. The Pathista template runs the tests on the release commit, loops through fixes for up to three rounds, checks that the tag points at the tested commit and opens the publish step only after your explicit yes.

The problem

A release has steps whose order matters: version, changelog, tests, tag, publish. Skipped or reordered, they give a tag on an untested commit or a package nobody confirmed. The template puts the steps in order and ties the risky ones to conditions.

How the template handles it

The two variables testsGreen and userConfirmed are set by the assistant from what happened in the chat. The evidence and your answer are in the run's log, so you can check both.

  • Tests run on the release commit. The step records the command, the commit id and the passed, failed and skipped counts, and sets testsGreen.
  • Red tests send the run to a fix step and back to the tests. If the tests are still red after three rounds of fixes, the only way out is to stop and report.
  • The tag is created on the tested commit and compared with the commit id of the green test summary; if they differ, the run goes back to the tests.
  • Before publishing, the assistant shows the version, the changelog, the test result, the tag and the exact commands, and asks a yes-or-no question. The way to the publish step is open only while testsGreen and userConfirmed are both true.
  • After publishing, the release is installed on a clean setup and run once.

Make it yours

Add the template to your workflows, then edit the steps to your project's commands. Every edit is saved as a new version, and a run keeps the version it started on. To use it with Claude Code, connect it first.

One step as an example

Words in code type, such as testsGreen, are the template's own variables: small yes/no values or counters that the assistant sets during the run and that decide which way out of a step is open.

The checklist of the step “Build and tests on the release commit”. The assistant may leave the step only when every item is closed with evidence:

  • 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)

Every step and checklist item is on the Release checklist for a Claude Code project template page.

Open the template

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.