commit

Commit

Automate the full git commit workflow in one shot. No user intervention needed between steps unless something looks wrong.

Important

Run all git commands directly (e.g., git status) without prefixing cd <path> &&. The Bash tool already runs in the project's working directory, and the cd prefix breaks permission allow-list matching on Bash(git *).

Steps

1. Gather context (run all three in parallel)

git status           # overview of staged, unstaged, untracked (NEVER use -uall)
git diff --stat      # summary of staged + unstaged changes
git log --oneline -5 # recent messages for style matching

2. Check for phase doc updates

Before drafting the commit message, scan the diff for changes that should be reflected in project docs. If changes touch phase deliverables (new API methods, schema changes, parser updates, etc.), check whether plan/master-plan.md or the relevant plan/phase-*.md file needs updating. If so, make those edits and include them in the commit. Don't create a separate commit for doc updates — bundle them together.

2b. Update phase document status

If the changes being committed implement work from a specific phase, update the phase's status in both the phase document and the master plan. This keeps the project's planning docs in sync with reality.

How to determine which phase is affected:

• Look at the files being changed and match them to phase deliverables
• Check commit message context (e.g., "Phase 55" in the message or branch name)
• If unsure, skip this step — only update when you're confident

What to update in the phase doc (plan/phase-*.md):

• Update the > **Status**: line in the header (e.g., Planning → In Progress, In Progress → Complete, or Planning → Partial if only some items were done)

What to update in plan/master-plan.md:

• Update the status column in the Active Plans table to match
• Update the phase heading in the Phased Implementation section (e.g., (PLANNING) → (IN PROGRESS) or (COMPLETE))