tool / ai

Commit Message Generator

Build Conventional Commit messages step by step — pick type, add scope, write a short description, flag breaking changes, and reference issues. Get a git branch name suggestion as a bonus.

← Back to tools

1Commit type

2Scope (optional)

The area of the codebase this commit affects.

3Short description

0/72

Use imperative mood: "add", "fix", "remove" — not "added" or "adds".

4Breaking change?

5Body (optional)

6Issue references (optional)

Reference issues or pull requests related to this commit.

Commit message
Fill in steps above to generate your commit message…

Conventional Commits

The Conventional Commits spec is a standard for writing human- and machine-readable commit messages. It powers automated changelogs, semantic versioning, and release pipelines.

Format reference

type(scope)!: description

Optional body explains the why.
Footer holds BREAKING CHANGE: and issue refs.
The ! signals a breaking change.

Tips for good commits

Keep the header under 72 characters. Use the imperative mood ("add", not "added"). A well-scoped commit is easier to review, revert, and cherry-pick — especially in fast-moving monorepos.

// huntermussel

Want to enforce commit conventions and automate releases in your pipeline?

HunterMussel sets up commitlint, semantic-release, and changelog generation so every merge produces a clean, versioned release — automatically.

Explore CI/CD & DevOps Engineering →