Commit

Commit Changes

You are tasked with creating git commits for the changes made during this session.

Process:

1. Think about what changed:

• Review the conversation history and understand what was accomplished
• Run git status to see current changes
• Run git diff to understand the modifications
• Consider whether changes should be one commit or multiple logical commits

2. Plan your commit(s):

• Identify which files belong together
• Draft clear, descriptive commit messages
• Use imperative mood in commit messages
• Focus on why the changes were made, not just what

3. Present your plan to the user:

• List the files you plan to add for each commit
• Show the commit message(s) you'll use
• Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"

4. Execute upon confirmation:

• Use git add with specific files (never use -A or .)
• Create commits with your planned messages
• Show the result with git log --oneline -n [number]

5. Generate reasoning (after each commit):

• Run: bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <commit-hash> "<commit-message>"
• This captures what was tried during development (build failures, fixes)
• The reasoning file helps future sessions understand past decisions
• Stored in .git/claude/commits/<hash>/reasoning.md

Important:

• NEVER add co-author information or Claude attribution
• Commits should be authored solely by the user
• Do not include any "Generated with Claude" messages
• Do not add "Co-Authored-By" lines
• Write commit messages as if the user wrote them

Remember:

• You have the full context of what was done in this session
• Group related changes together
• Keep commits focused and atomic when possible
• The user trusts your judgment - they asked you to commit

Option: commit

I (Initiation)

activate: [user_says_commit, user_says_push, feature_complete] skip: [uncommitted_changes_empty, mid_implementation]

Y (Observation Space)

U (Action Space)

primary: [Bash] forbidden: [co_author_lines, claude_attribution]

pi (Policy)

P0: Review Changes

eta |-> assess_changes via git_status, git_diff

P1: Plan Commits

eta |-> group_files_logically
eta |-> draft_messages (imperative mood, explain why)

P2: Request Approval

eta |-> present_plan_to_user
plan: {files: [...], message: "...", count: N}

P3: Execute

eta |-> git_add(specific_files)
eta |-> git_commit(message)
eta |-> generate_reasoning(hash, message)

Command Reference

git add <file1> <file2> ...
git commit -m "message"
bash "$CLAUDE_PROJECT_DIR/.claude/scripts/generate-reasoning.sh" <hash> "<message>"
git log --oneline -n N

beta (Termination)

beta(eta) = 1.0 if commits_created OR user_cancels

success: [commits_made, reasoning_generated, log_shown] failure: [no_changes, user_declined]

Output Schema

plan: {commits: [{files: [...], message: "..."}]}
result: {hashes: [...], log: "..."}

Invariants

inv_1: never include "Co-Authored-By" or "Generated with Claude"
inv_2: always use specific file paths (never git add -A)
inv_3: always generate reasoning.md after each commit