How do I undo my last commit without losing my changes?

Use the "Undo the last commit (keep changes)" recipe, which builds git reset --soft HEAD~1. The --soft flag moves your branch pointer back one commit but keeps all of that work staged, ready to recommit. Choose --mixed instead if you want the changes unstaged. Your files are never deleted — only the history pointer moves.

What is the difference between git reset and git revert?

git reset moves your branch pointer backwards and can rewrite or discard history, so it is best for commits you have not shared yet. git revert instead creates a new commit that undoes a previous one, leaving the original in place — which makes it safe to use on branches you have already pushed. The builder offers both so you can pick the right one for shared versus local work.

How do I force-push safely after a rebase?

Pick the "Safely force-push a rewritten branch" recipe, which uses git push --force-with-lease. Unlike the blunt --force, this refuses the push if the remote has commits you have not seen locally, so you cannot accidentally overwrite a teammate's work. It is the recommended way to push after rebasing or amending.

How do I stash only some of my changes?

The Stash recipes build git stash push with an optional message and an "include untracked files" toggle. By default Git stashes only tracked, modified files; tick the untracked option to also shelve brand-new files. To restore, use the pop recipe, which re-applies the most recent stash and removes it from the stack — or choose "keep" to apply without removing it.

How do I recover a commit I lost after a bad reset?

Use the "Recover a lost commit (reflog)" recipe. git reflog lists every position HEAD has pointed to recently, including commits orphaned by a reset, rebase, or deleted branch. Copy the hash from the relevant entry, then run git switch -c rescue to bring it back onto a new branch. Reflog entries persist for a while, so act reasonably soon.

Is anything I type sent to a server?

No. The Git Command Builder runs entirely in your browser. Branch names, file paths, commit messages and every option stay on your machine — nothing is uploaded, logged or transmitted. You can use it offline once the page has loaded.

Git Command Builder — Gera Tools

The Git Command Builder turns “I want to undo my last commit” or “I need to stash this and switch branches” into the exact git command to run — and, just as importantly, a plain-English explanation of what every flag does. It is built for anyone who knows roughly what they want from Git but cannot always remember the precise incantation, and would rather understand a command than blind-copy it from a random forum answer.

How it works

Pick an action from one of seven categories — Branches, Commit & staging, Undo & history, Stash, Rebase & sync, Remotes & push, and Inspect & search — or just type what you are trying to do in the search box (it matches on the action name, summary, and tags, so “uncommit”, “shelve”, or “who changed this line” all find the right recipe). Each recipe shows a small form with only the fields that command actually needs: a branch name, a commit reference, a file path, a message, plus toggles for the options that genuinely change behaviour, such as force-deleting, including untracked files, or keeping changes staged versus unstaged.

As you fill in the form the command is rebuilt live, with shell-safe quoting applied automatically so paths or messages containing spaces and special characters never break. Alongside the command you get a “What it does” breakdown that explains each part in everyday language, and — for the genuinely dangerous operations like git reset --hard or a force-push — a clearly highlighted caution so you know exactly what is at stake before you press Enter. Everything is computed in your browser; no command, path, or message ever leaves your machine.

Example

Say you just made a commit but forgot to include a file and want to fix the message too. Open the Amend the last commit recipe, type your corrected message, tick “Stage all tracked changes first”, and the builder produces:

git add -u && git commit --amend -m 'fix: correct typo in README'

with an explanation that amending rewrites the most recent commit (and a reminder that if you already pushed it, you will need a --force-with-lease push afterwards).

You want to…	The builder gives you
Undo last commit, keep work	`git reset --soft HEAD~1`
Throw away a file’s edits	`git restore src/app.ts`
Shelve work in progress	`git stash push --include-untracked`
Replay branch on latest main	`git fetch origin && git rebase origin/main`
Push safely after a rebase	`git push --force-with-lease origin`

Every command is generated locally — nothing is uploaded or stored.