status
Inspect tracked and untracked changes; does not commit them.
Reads repository information if you run it; no repository is inspected here.
Git & Version Control
Git command builderUnderstand before you run
Choose a template or inspect one command. Review its arguments and effects before taking it to a terminal.
Git command builder
Parameters or command
Command preview
git status
Quoting targets POSIX shells: sh, Bash, zsh and Git Bash. Check your repository before running.
Processed in this browser. No command execution, repository access or network request.
Options
Preview ready. Nothing was executed.
Use the Git command builder when you know the task but cannot remember the flag: a shallow clone, a compact history graph, or a diff of staged changes. Start with the read-only status preview and choose the smallest operation that answers your question.
A Git cheat sheet shows a fixed example. Here the preview changes with your actual branch, path and message, while the adjacent explanation makes the consequences visible. It never claims that a syntactically supported command fits your repository.
Why use this Git command builder?
Keep values together
The Git command builder quotes values as single POSIX arguments. A message containing spaces or an apostrophe stays one value; a path beginning with a dash is separated from options. Git may still interpret that path as a pathspec, so shell quoting is not the same as literal filename matching.
Put consequences beside the command
Inspect a supported command without sending it to an AI service. Each result shows the operation, parameter meanings and risk category. Hard reset and force-with-lease retain a warning even when every argument is syntactically valid.
Three checks before using a preview
01
Choose the comparison baseline
The default diff compares the working tree with the index. Enable staged changes to compare the index with HEAD, or supply a revision to change the baseline. The optional path limits the comparison to one Git pathspec.
02
Control when the result updates
Automatic updates wait 350 ms after editing. Switch them off to reveal the generate button, then use Ctrl/Cmd + Enter. Changing a field immediately disables copying until the result is refreshed.
03
Review replacement and workflow steps
Loading an example or clearing fields first opens a replacement preview. Apply it, then undo once to restore input and output. Workflow recipes contain separate lines: check each result before running the next line yourself.
From inspection to an explicit change
Ten focused operations
The Git command generator covers status, clone, log, diff, switch, add, commit, fetch, push and reset. Clone accepts a branch and depth; log offers a count, graph and all refs. Hidden fields never become options for unrelated commands.
A bounded command explainer
The Git command explainer accepts one literal command and recognizes the same option subset. Known aliases such as --staged and --cached share a meaning. Unknown flags, duplicate options, incomplete quotes and extra arguments stop the result instead of being silently ignored.
Three readable workflows
Inspect changes with status, diff and log; create a branch with status, switch -c and status; prepare a commit with status, add and commit. Recipes preserve your fields when selected and never decide whether it is safe to continue after a failed step.
What the preview cannot verify
- No repository state or execution
- The page cannot confirm branches, commits, permissions, conflicts, hooks or configuration. It does not install Git, execute a command or reverse anything run in your terminal. A successful preview confirms only this tool’s supported syntax.
- One shell family and a small grammar
- Output targets POSIX shells, including Git Bash, rather than PowerShell or CMD. The explainer rejects scripts, pipes, redirections, expansions, aliases and global Git options. Merge, rebase, clean, ordinary --force and remote deletion are outside its templates.
- Inputs have explicit limits
- Use up to 8,192 characters per explained command and 2,048 per field. Control characters and invalid Unicode are rejected. Optional history counts accept 1–1000 and clone depth 1–1000000; an empty count leaves Git’s own limit unchanged.
- Names and addresses are restricted
- Clone supports HTTPS without credentials, SSH without passwords and user@host:path addresses, not local paths or remote helpers. Branches use ordinary ASCII names; revisions add simple ~ or ^ ancestry suffixes. Existing refs are not resolved, and complex revision expressions are rejected.
- Destructive flags stay destructive
- Reset soft moves HEAD, mixed also resets the index, and hard discards tracked work and may remove obstructing untracked paths. Force-with-lease can replace remote history; background fetch can weaken its expected-ref protection. No generated preview guarantees recoverability.
Git command builder FAQ
How do I build git commands online?
Choose an operation and fill the relevant fields. The form produces a command preview with explanations. Check the target repository and shell before copying; generating text does not run Git.
How do I undo a commit while keeping my work?
For an unshared last commit, reset --soft HEAD~1 moves the branch back while retaining the index and working files; mixed also unstages the changes. Inspect your history first. Published commits usually require a different collaboration decision, often a new revert commit; this page does not provide a revert template.
What is the difference between git diff --cached and --staged?
For git diff, --cached and --staged are synonyms. Both compare the index with HEAD when no revision is supplied. Plain git diff shows unstaged tracked changes, so an empty diff does not mean there is nothing staged to commit.
Does it explain every git command?
No. It covers the ten named subcommands with the displayed flags, ordinary names and simple revisions. Commands involving aliases, global options, shell expansion or unsupported flags are rejected. Consult the Git manual for those cases.
Is my command sent to a server?
No command text or field values are sent for analysis, and there is no saved history or share link containing them. Clipboard access happens only when you click Copy.
Does a preview differ from your device’s documented syntax?
Review a command with its consequences
Return to the Git command builder, select a read-only template first, and inspect the exact parameters. Copy the current result only after its meaning matches your intended operation.