commit-format

To format git commit messages using Conventional Commits, provide a commit title and optional description to generate structured output with semantic types like feat:, fix:, or chore:, wrapping the title in a single backtick pair.

Conventional Commits formatting supports semantic types including feat: for features, fix: for bug fixes, perf: for performance, refactor: for code restructuring, docs: for documentation, and chore: for maintenance tasks.

A description is optional when writing conventional commit messages. The format requires a mandatory title wrapped in a single backtick pair, while the description can be added to provide additional context for the code changes.

The best way to structure commit messages for code collaboration is enforcing a Conventional Commits format with a mandatory title and optional description, ensuring a clear and consistent git history across proposed changes.

Use conventional commit formatting when proposing or implementing code changes, writing commit messages, or generating AI-assisted commit suggestions during code collaboration to enforce clear semantics and maintain a consistent repository history.