kirocc: Skill for Claude Code

Release

Automate the kirocc release process. Takes a version argument (e.g., /release-kirocc v0.1.0).

Prerequisites

• gh CLI installed and authenticated
• Write access to d-kuro/kirocc

Release Flow

The release is a two-phase process. Phase 1 prepares the release (branch, notes, PR). Phase 2 happens after the PR is merged (tag, publish, sync notes). Guide the user through each step, confirming before destructive or visible actions.

Phase 1: Prepare Release

Step 1 — Determine version

Parse the version from the argument. If not provided, ask the user. The version must follow semver format: vX.Y.Z (with leading v). If the user gives a version without the v prefix, add it.

Find the previous tag to use for changelog comparison:

git tag --sort=-v:refname | head -1

If no previous tag exists, use the first commit as the base.

Step 2 — Update main and create release branch

git checkout main
git pull origin main
git checkout -b release/<version>

Step 3 — Find changes since last release

Gather PR information for release notes. Find the date of the previous tag (or use repo creation date if first release):

PREV_TAG=$(git tag --sort=-v:refname | head -1)
if [ -n "$PREV_TAG" ]; then
  SINCE=$(git log -1 --format=%aI "$PREV_TAG")
else
  SINCE=$(git log --reverse --format=%aI | head -1)
fi

List merged PRs since that date:

gh pr list --state merged --search "merged:>$SINCE" --json number,title,author,labels

Step 4 — Find external contributors

Exclude the maintainer and bots:

gh pr list --state merged --search "merged:>$SINCE" \
  --json number,title,author \
  --jq '.[] | select(.author.login != "d-kuro" and (.author.login | test("\\[bot\\]$") | not)) | "- @\(.author.login) (#\(.number))"'

If no external contributors, omit the Contributors section from the release notes.

Step 5 — Write release notes

Create docs/release-notes/<version>.md using the template below. Categorize PRs by their content. Omit empty sections.