rollback

/rollback - Safe Rollback

$ARGUMENTS

What This Command Does

Safely revert changes with appropriate safety checks and confirmation.

Rollback Types

1. Git Rollback

# Revert last commit (creates new commit)
git revert HEAD --no-edit

# Revert specific commit
git revert <commit-sha> --no-edit

# Revert to specific state (CAUTION)
git reset --soft <commit-sha>  # Keep changes staged

2. Database Migration Rollback

Tool	Command
Alembic	alembic downgrade -1
Prisma	npx prisma migrate resolve --rolled-back <name>
Laravel	php artisan migrate:rollback --step=1
Django	python manage.py migrate <app> <previous>
Flyway	flyway undo

3. Deployment Rollback

Platform	Command
Kubernetes	kubectl rollout undo deployment/<name>
Docker Compose	docker compose up -d --force-recreate (with previous image tag)
Heroku	heroku rollback

Gather Rollback Context

Run the rollback info script to assess current state before rolling back:

python3 ${CLAUDE_SKILL_DIR}/scripts/rollback_info.py

Returns JSON with:

• git{} - current/previous commit, branch, commits ahead, uncommitted changes
• migrations{} - detected tool (alembic/prisma/laravel/django/drizzle), rollback command
• docker{} - running services and image tags

Safety Checks (MANDATORY)

Before any rollback:

1. Confirm what will be reverted (show diff/plan)
2. Check for dependent changes that may break
3. Verify backup exists (for database rollbacks)
4. Get explicit user confirmation

Usage Examples

/rollback                    # Interactive - asks what to rollback
/rollback git last           # Revert last git commit
/rollback migration          # Rollback last database migration
/rollback deploy             # Rollback to previous deployment

CRITICAL: Always confirm with the user before executing destructive rollback operations.

Rules

• MUST confirm the current state AND the target state before rolling back — surface the diff in plain English
• MUST verify a recent backup exists (for DB rollbacks) or explicitly warn the user that none was found
• NEVER roll back without an explicit "yes" from the user — rollbacks are irreversible in the user-experience sense even when technically reversible
• NEVER git reset --hard on a branch others have pulled from — it rewrites shared history
• CRITICAL: after any rollback, run a health check (/health or the project's equivalent) to confirm the target state is stable — a "successful" rollback to a broken baseline is worse than the original state
• MANDATORY: log the rollback with timestamp, scope, and reason — post-mortems need this trail