/git is the final stage of the pipeline. It runs pre-ship verification, then handles commit messages, branch operations, and the merge or PR decision using safe defaults and structured protocols.
Pre-ship verification
Before any git operation that ships code, SuperAntigravity loads the verification-before-completion skill. No completion claims are made without fresh verification evidence — meaning the test suite is run in full and the output is read before any success claim is made. Then the finishing-a-development-branch skill presents exactly four options:Smart commit protocol
For individual commits during/implement or when running /git directly:
1
Run git status
Understand what changed. Never commit blindly.
2
Run git diff
Review actual changes before staging anything.
3
Stage specific files
Stage only the files that belong to this commit.
git add . is never used blindly.4
Generate commit message
Write a message following Conventional Commits format (see below).
5
Commit
Commit with the generated message.
Commit message format
All commit messages follow Conventional Commits:During
/implement, commits use the test: prefix with the format test: [what behavior is now tested]. This links each commit directly to the behavior it verifies.Branch naming
| Type | Pattern | Example | |------|---------|---------|| | Feature |feat/description | feat/user-auth |
| Fix | fix/description | fix/token-expiry |
| Experiment | experiment/description | experiment/new-cache-layer |
Common operations
Safety rules
These rules are enforced unconditionally: If you explicitly request a force push tomain or master, SuperAntigravity will warn you and ask for confirmation before proceeding.
Finishing a development branch
When SuperAntigravity reaches the end of/implement, the finishing-a-development-branch skill guides the merge or PR decision:
1
Verify tests
Runs the full test suite. If tests fail, the process stops here. Merge or PR options are not presented until tests pass.
2
Determine base branch
Identifies the branch this feature branched from — typically
main or master.3
Present options
Shows the four structured options (merge locally, create PR, keep as-is, discard).
4
Execute choice
Runs the chosen option. For a local merge, runs tests on the merged result before deleting the feature branch. For a PR, pushes the branch and creates the PR with a summary and test plan.
5
Clean up worktree
Removes the worktree for options 1 (merge) and 4 (discard). Keeps the worktree for options 2 (PR) and 3 (keep as-is).