release

name	release
description	Use this skill when the user wants to merge the dev branch into master and ship a release. Triggers include phrases like "release", "deploy", "ship it", "リリース", "デプロイ", "master にマージしてデプロイ", "本番リリース". Verifies a clean working tree, switches to master, fetches origin --prune, confirms master matches origin/master, merges dev with --no-ff, then runs deploy.sh with the minor/patch bump confirmed up front. Streams deployer output to the user and reports success or failure at the end.
version	1.0.0

release

Merge dev into master and run deploy.sh to publish the next release. The skill performs a hard-stop at any unexpected state — it never tries to "fix" the situation on its own.

When to use

Invoke this skill when the user expresses any of the following intents:

• "Release", "deploy", "ship it", "publish a new version"
• "リリース", "デプロイ", "master にマージしてデプロイ", "本番リリース"
• Wanting to cut a new minor or patch release from the current dev

Procedure

Run the steps below in order using the Bash tool. Proceed to the next step only if the previous one succeeds. If anything unexpected happens, stop and report to the user — do not attempt recovery automatically.

Step 0: Confirm version bump

Before touching git, ask the user whether this release is a minor or patch bump. Use AskUserQuestion with these two options. Save the answer; it will be passed to deploy.sh in the final step.

This must happen up front so the long-running deploy is not blocked waiting for input later.