Commit

Write a commit message that follows the project's conventions and clearly explains what changed and why.

Steps

1. Run git diff --cached (or git diff if nothing is staged) to see all changes.
2. Run git log --oneline -5 to match the project's existing commit style.
3. Analyze the changes:
   • What was added, changed, or removed?
   • Is this a feature, bug fix, refactor, docs update, or chore?
   • What is the motivation behind the change?
4. Write the commit message:
   • First line: imperative mood, under 72 chars (e.g., fix: prevent duplicate API calls on rapid tap).
   • Body (if needed): blank line, then explain why, not what.
   • Match the project's commit style (conventional commits, prefixes, etc.).
5. Stage only relevant files. Don't git add . blindly — exclude generated files, secrets, unrelated changes.
6. Create the commit.