Commit
- •Stage all changes (prefer specific files over
git add -A) - •Run
git diff --cachedto analyze what's staged - •Craft a commit message:
- •Subject: emoji + one sentence about WHY this change exists (not what changed)
- •Body: what this unlocks, alternatives you considered, why this approach was chosen
- •Never describe what changed — the diff speaks for itself
- •After committing, check the current branch. If it is NOT main or master, push automatically.
Subject line examples
- •
🔒 Secure personal information - •
🍼 Provide new parents with tools - •
🧹 Reduce friction for future changes - •
📬 Let subscribers know when plans change
Format
code
git commit -m "$(cat <<'EOF' <emoji> <Why this change exists> <What this unlocks or enables. Alternatives considered. Why this approach.> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> EOF )"