Write Commits

Generate commit messages following repository conventions.

Instructions

Step 1: Analyze Staged Changes

bash
1git diff --cached --stat
2git diff --cached

Identify:

• Files changed and their paths
• Nature of changes (new feature, bug fix, refactor, etc.)

Step 2: Write Commit Message

Format:

text
1Subject in imperative mood
2
3- Body bullet in past tense with period (only if subject isn't enough).
4- Another change description.

Rules:

• Subject: imperative mood, capital start, no period, max 72 chars
• Body: only include when subject line alone doesn't adequately describe the changes
• Body bullets: past tense, capital start, period at end
• No attribution (no "Co-Authored-By" or "Generated with")

Step 3: Output

Provide the commit message ready to use. Only include a body when the subject line alone isn't sufficient to describe the changes.

Examples

Simple change:

text
1Add task details dialog

Change with body (subject alone isn't enough):

text
1Add task details dialog
2
3- Added OrderDetailsDialog with map preview and navigation.
4- Extracted filtering and pagination into reusable hooks.

Bug fix:

text
1Correct button disabled state styling

Refactor with body (subject alone isn't enough):

text
1Simplify locale resolution logic
2
3- Replaced manual locale matching with Intl.LocaleMatcher.
4- Removed fallback chain in favor of single default.

Configuration update with body (multiple changes):

text
1Update workspaces and dependencies
2
3- Added shared/repositories/* to workspaces.
4- Bumped @biomejs/biome to 2.3.8.