Git Conventional Commits

Analyze working tree changes, group by intent, write conventional commit messages that respect repo conventions.

References (read when needed):

• references/worked-example.md — read when grouping is ambiguous or changes span multiple intents

Workflow

Step 1: Detect repo conventions

Do this before writing any messages. Repo-specific rules override defaults here.

• Check .commitlintrc*, commitlint.config.*, .czrc, CONTRIBUTING.md
• Always run git log --oneline -20 — even when config files exist. Config defines the rules; history shows what the team actually does. When they conflict, history wins.

Repo history is the ground truth. A feat: in a repo that uses feature: looks wrong forever.

Step 2: Assess the working tree