Slash Command

/rollback

Rollback a deployment to previous version

Install

Run in your terminal

npx claudepluginhub LeanEntropy/civax-cc-agents --plugin railway-deployer

Allowed Tools

BashReadGrepmcp__Railway__*

Command Content

Other plugins with /rollback

/rollback

Rolls back the most recent database migration or to a specific version, with data loss warnings, explicit confirmation, transactional execution, schema verification, and status report.

migration-generator

1.0k

/rollback

Reverts to a previous Shipyard checkpoint via git tag, with state-only or full code scope. Supports --list flag; prompts for checkpoint and scope if needed.

shipyard

/rollback

Safely rollbacks a failed or unwanted feature by invoking /specswarm:rollback with optional flags (--dry-run, --keep-artifacts, --force).

/rollback

Rollbacks orchestrator project state to a specified checkpoint ID, restoring task status and optionally resetting Git commit. Lists available checkpoints if none provided.

ReadWriteBash

orchestrator

/rollback

workflow/

Reverts git repository to checkpoint before specified phase number after previewing changes and user confirmation. Also lists checkpoints with --list.

aura-frog

/rollback

Rollback a deployment

BashReadWrite

deployment-pipeline

Stats

Parent Repo Stars0

Parent Repo Forks0

Last CommitDec 30, 2025

Actions

View Source View Plugin View on GitHub View README

Rollback Command

Rollback a deployment to a previous version.

Usage

/railway-deployer:rollback [staging|production] [--to <commit|tag>]

Rollback Methods

Method 1: Git Revert (Recommended)

Creates a new commit that undoes changes. Preserves history.

git revert <commit-hash>
git push origin main
# Railway auto-deploys the revert

Method 2: Railway Dashboard

Rollback to specific deployment in Railway UI:

Go to Railway Dashboard
Select Service → Deployments
Click "Rollback" on previous healthy deployment

Method 3: Hard Reset (Emergency Only)

Warning: Rewrites history, requires force push.

git reset --hard <commit>
git push --force origin main  # DANGEROUS

Interactive Workflow

Rollback Production
===================

Current deployment:
  Commit: abc1234 (feat: new feature)
  Deployed: 30 minutes ago
  Status: unhealthy ⚠️

Recent deployments:
  1. abc1234 - feat: new feature (30m ago) ⚠️
  2. def5678 - fix: bug fix (2h ago) ✓
  3. ghi9012 - Release v1.2.0 (1d ago) ✓

? Rollback to which deployment?
  > def5678 - fix: bug fix
    ghi9012 - Release v1.2.0
    Enter specific commit/tag

? Rollback method:
  > Git revert (recommended)
    Railway rollback
    Git reset (dangerous)

Creating revert commit...
✓ Reverted abc1234
✓ Pushed to origin/main
✓ Railway deployment triggered

Monitoring rollback...
✓ Build successful
✓ Deployment healthy

Rollback complete!
Production is now running: def5678

When to Rollback

Immediate Rollback Needed

Application crashes on startup
Critical functionality broken
Security vulnerability discovered
Data corruption risk

Can Wait for Fix

Minor UI bugs
Non-critical feature broken
Performance degradation (if tolerable)

Post-Rollback Actions

Verify production is healthy
Investigate root cause
Fix issue on develop branch
Test thoroughly in staging
Re-deploy when ready

Emergency Contacts

For critical production issues:

Check Railway status: https://status.railway.app
Railway Discord: https://discord.gg/railway
Supabase status: https://status.supabase.com