rollback

name	rollback
description	Roll back a deployment to the previous stable version

Skill: rollback

Load Context

1. Read $ARGUMENTS for the target environment and optional target version. If environment is empty, ask the user.
2. Read docs/RELEASE.md for rollback steps
3. Run git log --oneline -20 to review recent version history
4. If a deployment history file exists (e.g. deploy-history.json), read the last two entries

Pre-checks

• If target is production and this is not auto-triggered by a smoke test failure → require the user to type yes to confirm.
• If the previous stable version cannot be determined → list the last 5 commits and ask the user to specify the rollback target.
• If the current version and the previous version are the same → abort: "Already at the oldest available version."

Steps

Step 1: Confirm rollback target

Print current and target versions:

Current version: <commit hash> - <commit message> (<timestamp>)
Rollback target: <commit hash> - <commit message> (<timestamp>)

Environment: <environment>

Confirm rollback? (yes/no)

• Auto-triggered (from smoke test failure) → skip confirmation, proceed immediately, note "auto-triggered" in the report
• Manually triggered → wait for the user to type yes

Step 2: Execute rollback

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

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

If any rollback step fails → stop immediately, go to Error Handling.

Step 3: Wait for service readiness

Same as in the release skill: poll the health check endpoint for up to 5 minutes.

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

Step 4: Verify the rollback

Re-run smoke tests against the rolled-back version (critical paths only, no recursive rollback trigger):

• All pass → rollback successful
• Failures → rolled-back version also has issues, go to Error Handling

Step 5: Output rollback report

Success:

✅ Rollback complete: <environment>

Rolled back from: <old commit hash>
Rolled back to:   <target commit hash>
Timestamp:        <ISO timestamp>
Trigger:          <manual / auto-triggered by smoke test>

Service status: healthy (smoke tests passed)

Recommended next steps:
  1. Investigate why the original version failed
  2. Fix and redeploy when ready

Failure:

❌ Rollback failed: <environment>

Failed step: <step description>
Error: <error details>

⚠️ Manual intervention required.
Access the deployment platform directly to restore service.

Error Handling

Situation	Action
A rollback step fails	Stop execution, print full error output, clearly state "manual intervention required" — do not attempt further automated recovery
Smoke tests still fail after rollback	Print report, note "rolled-back version is also broken", do not trigger another rollback, wait for manual action
docs/RELEASE.md has no rollback steps	Abort: "No rollback steps found in RELEASE.md. Please add them, or roll back manually via the deployment platform."
Cannot determine the previous version	List recent git tags and commits, ask the user to specify the target version manually

Done When

• Current and target versions were clearly identified before execution
• User confirmed (or action is logged as auto-triggered)
• All rollback steps completed successfully
• Smoke tests pass on the rolled-back version
• Rollback report printed (includes versions, timestamp, and trigger reason)