Goal Release

new_version = the user's request

This skill drives a release all the way to merge. It uses the draft-release skill to open the release pull request (and create the draft GitHub release), waits for the PR's CI checks to pass, runs the merge-pr skill to merge it, and finally updates the Homebrew tap formula once the release assets are built.

1. Draft the Release

Use the draft-release skill with new_version.

• If new_version is provided (e.g. v1.2.3 or 1.2.3), it must match the semver shape ^v?\d+\.\d+\.\d+$, if it does not, stop and report instead of passing it on. Pass a valid value through unchanged; the draft-release skill normalizes the v prefix itself.
• If new_version is empty, pass no argument; the draft-release skill determines the next version automatically via the release-dry-run skill.

When the draft-release skill finishes, it has:

• created a release/v<version> branch with the version-bump commits,
• opened a pull request against main, and
• created a draft GitHub release v<version> with the release notes.

If the draft-release skill failed partway (e.g. the PR exists but the draft release was not created, or it stopped before opening the PR), stop here and report the partial state to the user instead of continuing.

2. Resolve the Release PR

Use the PR number or URL that the draft-release skill's gh pr create printed in Step 1 when available. Otherwise, identify the pull request from the current release/v<version> branch:

gh pr view --json number,title,state,headRefName

Confirm that headRefName matches the release/v<version> branch created in Step 1. This skill must only ever merge that release PR, if the resolved PR is a different one, stop and report to the user instead of merging.

3. Wait for CI

Wait for the release PR's GitHub Actions checks to finish:

gh pr checks <pr_number> --watch