Emergency Rescue Kit

Step-by-step recovery procedures for the worst moments in a developer's day. Every section follows the same pattern: diagnose → fix → verify. Commands are non-destructive by default. Destructive steps are flagged.

When something has gone wrong, find your situation below and follow the steps in order.

When to Use

• Someone force-pushed to main and overwrote history
• Credentials were committed to a public repository
• A rebase or reset destroyed commits you need
• Disk is full and nothing works
• A process is consuming all memory or won't die
• A database migration failed halfway through
• A deploy needs to be rolled back immediately
• SSH access is locked out
• SSL certificates expired in production
• You don't know what went wrong, but it's broken