Fast Commit

Analyze staged changes and commit instantly with a well-crafted conventional commit message. No confirmation step — speed is the point.

Step 1: Check for staged changes

Run git diff --cached --stat to see what's staged.

If nothing is staged, check git status for unstaged changes. If there are unstaged changes, tell the user nothing is staged and suggest they stage files first. Do not run git add unless the user explicitly asks you to. If the repo is clean, say so and stop.

Step 2: Gather context

Run these in parallel:

• git diff --cached — the full staged diff (this is the primary input for the commit message)
• git log --oneline -20 — recent commit history, so you can match the project's existing scope conventions
• git branch --show-current — the branch name often encodes intent (e.g., fix/null-user-lookup, feat/oauth-google)

Conversation context: Before analyzing the diff, review what the user has been working on in this conversation. Tasks they described, bugs they debugged, or features they built are the strongest signal for the why behind a change. Prefer conversation context over guessing intent from code alone.