release

name	release
description	Deploy the current release to a target environment

Skill: release

Load Context

1. Read $ARGUMENTS for the target environment (staging / production). Default to staging if empty.
2. Read docs/RELEASE.md for the project's deployment procedure
3. Run git log --oneline -10 to confirm the current HEAD
4. Check CI status: gh run list --branch main --limit 5

Pre-checks

• If target is production:
  • Require explicit confirmation: "You are about to deploy to production. Type yes to confirm." Abort on anything other than yes.
  • Verify staging has been successfully deployed and smoke tests passed.
• If the most recent CI run status is not success → abort: "CI is not passing. Fix it before deploying."
• If critical unmerged PRs exist → warn the user (do not abort).

Steps

Step 1: Pre-deploy checks

Work through the checklist in .claude/hooks/pre-deploy.md:

• CI passing ✓ (verified in pre-checks)
• Confirm the version to deploy (current HEAD commit hash)
• Target environment health check (if a health endpoint exists)

Step 2: Execute deployment

Follow the deployment steps in docs/RELEASE.md exactly — do not skip any step.

Print progress for each step:

[1/N] Running: <step description>
      Result:  ✓ success / ✗ failed (<error summary>)

If any step fails → stop immediately, go to Error Handling. Do not continue to subsequent steps.

Step 3: Wait for service readiness

If the deployment is asynchronous (e.g. rolling container update), poll the health check endpoint for up to 5 minutes:

Waiting for service to be ready... (30s / 60s / 90s / ...)

Timeout → treat as deployment failure, go to Error Handling.

Step 4: Post-deploy actions

• Record deployment version and timestamp (print for user to archive)
• Trigger the smoke-test skill

Step 5: Handle smoke test result

• All pass → print success report, deployment is complete
• Any failure → automatically trigger rollback (production) or inform the user to decide (staging)

Step 6: Output deployment report

✅ Deployment successful: <environment>

Version:      <commit hash>
Timestamp:    <ISO timestamp>
Smoke tests:  N passed

[staging]    Next: confirm functionality, then run /release production
[production] Next: monitor error rate for 15 minutes

Error Handling

Situation	Action
A deployment step fails	Print the failed step and error, do not continue, ask the user to check CI/CD logs
Health check times out	Mark deployment failed, trigger rollback (production) or notify user (staging)
Smoke tests fail	Trigger rollback automatically (production); print failure details and wait for user decision (staging)
docs/RELEASE.md has no steps for the target environment	Abort: "No deployment steps found for <environment>. Please update RELEASE.md."

Done When

• All deployment steps completed successfully
• Service health check passes
• Smoke tests all pass
• Deployment report printed (includes version and timestamp)