1.9 KiB
1.9 KiB
description
| description |
|---|
| Create commits with user approval and no Claude attribution (supports git and jj) |
Commit Changes
You are tasked with creating commits for the changes made during this session. This command supports both git and Jujutsu (jj) version control systems.
Process:
-
Think about what changed:
- Review the conversation history and understand what was accomplished
- Check current changes:
- For git users:
git statusandgit diff - For jj users:
jj statusandjj diff
- For git users:
- Consider whether changes should be one commit or multiple logical commits
-
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 include in 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:
- For git users:
- Use
git addwith specific files (never use-Aor.) - Create commits with your planned messages:
git commit -m "message" - Show the result with
git log --oneline -n [number]
- Use
- For jj users:
- Changes are automatically tracked
- Create a new change with description:
jj describe -m "message" - Show the result with
jj log -n [number]
- For git users:
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