name	git-commit
description	Stage meaningful diffs and create Conventional Commits with WHY-focused messages

Git Commit

Create Conventional Commits (1.0.0) with WHY-focused messages.

Inspect the repository state first:

git status --short
git diff --stat            # unstaged
git diff --cached --stat   # staged
git log --oneline -10      # style reference

Breaking changes: only feat!: / fix!: may carry !. If a refactor/style/docs/chore changed behavior, it is misclassified — recategorize as feat or fix.
Message philosophy (t-wada): code describes HOW, tests describe WHAT, commit log describes WHY, code comments describe WHY NOT. The body explains reasoning and motivation — what problem, why now, why this approach over alternatives — not a restatement of the diff.
Subject: imperative mood, under 50 characters.
One logical unit per commit. Use git add -p <file> when a file mixes unrelated changes, and split into multiple commits, one at a time.

name	git-commit
description	Stage meaningful diffs and create Conventional Commits with WHY-focused messages

Create Conventional Commits (1.0.0) with WHY-focused messages.

Inspect the repository state first:

git status --short
git diff --stat            # unstaged
git diff --cached --stat   # staged
git log --oneline -10      # style reference

Breaking changes: only feat!: / fix!: may carry !. If a refactor/style/docs/chore changed behavior, it is misclassified — recategorize as feat or fix.
Message philosophy (t-wada): code describes HOW, tests describe WHAT, commit log describes WHY, code comments describe WHY NOT. The body explains reasoning and motivation — what problem, why now, why this approach over alternatives — not a restatement of the diff.
Subject: imperative mood, under 50 characters.
One logical unit per commit. Use git add -p <file> when a file mixes unrelated changes, and split into multiple commits, one at a time.

git-commit