Conventional commit message

Write the commit message for the staged changes.

Format

<type>(<optional scope>): <summary>

• type: feat, fix, docs, style, refactor, perf, test, build, ci, or chore.
• summary: imperative mood, lower-case, no trailing period, 72 chars or fewer.
• Add a body (blank line, then prose) only if the why isn't obvious from the summary.
• Note breaking changes with a BREAKING CHANGE: footer.

Rules

• One logical change per commit — if the diff does two things, suggest splitting it.
• Describe the effect, not the list of files.

Example

feat(auth): add password reset via emailed link

Lets users recover access without contacting support.