Add option to make commit messages follow Conventional style including scopes

[beeltec]

It would be helpful to add an option that ensures commit messages follow the Conventional Commits specification. This provides a consistent commit format that improves readability, automation, and changelog generation.

What are Conventional Commits?

Conventional Commits define a structured format for commit messages:

<type>(<scope>): <description>

• type — The category of change
• scope (optional) — The part of the codebase affected
• description — A short summary of the change

Common types

Examples of commonly used commit types:

• feat — A new feature
• fix — A bug fix
• docs — Documentation changes
• style — Formatting or stylistic changes (no code behavior changes)
• refactor — Code restructuring without changing behavior
• test — Adding or updating tests
• chore — Maintenance tasks (dependencies, tooling, etc.)

Scopes

Scopes allow specifying the area of the project affected by the change. This helps make commit history easier to understand in larger projects.

Examples:

feat(auth): add OAuth login support
fix(api): handle null response in user endpoint
docs(readme): update installation instructions
refactor(parser): simplify token handling

Scopes are optional but recommended when changes affect a specific module or component.

[MatejSkarka]

+1 for this, would for sure use this.

[nathanscain]

+1 I have to make commits myself since my org enforces conventional commits