The Git Emergency Rescue & Command Lookup provides instant terminal recipes to undo common version control mistakes and recover lost work safely.

### Common Version Control Recovery Scenarios The tool organizes field-tested command recipes across six critical emergency categories: - **Wrong Branch Commits**: Move an accidental commit from main to a new feature branch without rewriting history ("git branch new-feature", "git reset HEAD~ --hard", "git checkout new-feature"). - **Accidental Secret Commits**: Soft-reset a commit containing credentials or ".env" files ("git reset HEAD~1"), add secrets to ".gitignore", and recommit cleanly. - **Commit Message Typos**: Modify the latest commit title without generating an unnecessary merge commit ("git commit --amend -m "...""). - **Discarding Messed-Up Work**: Realign a broken local branch completely with the remote tracking origin ("git reset --hard origin/branch"). - **Uncommitting Without Losing Code**: Undo a premature commit while preserving all staged modifications in your working directory ("git reset --soft HEAD~1"). - **Recovering Lost Commits**: Query the Git reference log ("git reflog") to resurrect commits orphaned after an aggressive hard reset.

### Practical Rescue Example An engineer accidentally commits AWS credentials to their local staging branch: 1. Select the **Security** category filter or search for "secret". 2. Copy the recovery command: "git reset HEAD~1". 3. The commit is undone while your code remains intact in the working tree. 4. Add ".env" to your ".gitignore" file and safely re-commit the remaining code.

### In-Browser Processing & Privacy Note All search filtering and emergency command lookup logic execute locally in your web browser. No Git repositories, command histories, or terminal outputs are uploaded to any server.