Committing Changes
Create git commits for changes made during the current session.
Workflow
- •
Assess changes
- •Review conversation history to understand what was accomplished
- •Run
git statusandgit diffto see current changes - •Decide: one commit or multiple logical commits?
- •
Plan commits
- •Group related files together
- •Draft commit messages in imperative mood ("Add feature" not "Added feature")
- •Focus on why changes were made, not just what
- •
Execute
- •
git addwith specific files (NEVER use-Aor.) - •
git commit -m "<message>" - •Repeat for each logical commit
- •
- •
Verify
- •
git log --oneline -n <number>to show results
- •
Rules
- •NEVER commit
thoughts/or anything inside it - •NEVER commit dummy files, test scripts, or artifacts not part of the actual changes
- •NEVER add co-author information or Claude attribution
- •Keep commits focused and atomic
- •Use your judgment on grouping - the user trusts you to commit