1# Commit Changes
 2
 3You are tasked with creating git commits for the changes made during this session.
 4
 5## Process:
 6
 71. **Think about what changed:**
 8   - Review the conversation history and understand what was accomplished
 9   - Run `git status` to see current changes
10   - Run `git diff` to understand the modifications
11   - Consider whether changes should be one commit or multiple logical commits
12
132. **Plan your commit(s):**
14   - Identify which files belong together
15   - Draft clear, descriptive commit messages
16   - Use imperative mood in commit messages
17   - Focus on why the changes were made, not just what
18
193. **Present your plan to the user:**
20   - List the files you plan to add for each commit
21   - Show the commit message(s) you'll use
22   - Ask: "I plan to create [N] commit(s) with these changes. Shall I proceed?"
23
244. **Execute upon confirmation:**
25   - Use `git add` with specific files (never use `-A` or `.`)
26   - Create commits with your planned messages
27   - Show the result with `git log --oneline -n [number]`
28
29## Important:
30- **NEVER add co-author information or Claude attribution**
31- Commits should be authored solely by the user
32- Do not include any "Generated with Claude" messages
33- Do not add "Co-Authored-By" lines
34- Write commit messages as if the user wrote them
35
36## Remember:
37- You have the full context of what was done in this session
38- Group related changes together
39- Keep commits focused and atomic when possible
40- The user trusts your judgment - they asked you to commit