commit

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

Process:

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
- Check if the user ran the following cursor command: /cleanup-ai-slop, and if not prompt them to do it first
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
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?"
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]
Push/sync changes:
- After committing, push the changes to the remote branch
- Use git push (or git push -u origin <branch> if the branch doesn't have an upstream)
- Confirm the push was successful

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
Keep descriptions concise, lowercase, and in present tense without periods.
Use Conventional Commits format: <type>(scope): <description>. Scope is optional. Use types like feat:, fix:, chore:, docs:, refactor:, perf:, test:. Add ! for breaking changes (e.g., feat!: or feat(api)!:).