How to use the Git Command Generator.
A Git command plan should start from the repository state and desired outcome. Explain destructive commands and prefer reviewable steps where possible.
Make the workflow fit your task.
Start from the repository state and desired outcome, then propose commands with their effects and review points. Keep inspection separate from mutations and identify operations that could discard or rewrite work.
- What you provide
- Repository task and current state description.
- What you get
- Explained command plan with destructive steps clearly marked.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Generate read-only Git commands to inspect uncommitted changes before preparing a commit.
Completed example
git status --short git diff git diff --staged Review: status includes untracked paths; git diff shows unstaged tracked-file changes; git diff --staged shows staged changes. Untracked file contents require separate inspection. None of these commands stages or commits files.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a Git command plan assume all uncommitted changes belong to one task?
Inspect the diff and repository state first. Stage only the work intended for the commit rather than treating every file as automatically related.
Why does a suggested command affect more history or files than intended?
Review the target, flags and current branch before running it. Git commands depend on state as well as syntax.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑