New: watch your coding agents work, step by step, on a live board. Try the demo, no account

Free tools

Conventional commits generator

A Conventional Commit starts with a type, an optional scope in parentheses, an optional ! for breaking changes, a colon and a space, then a short description: feat(parser): add array parsing. This builder writes that line, plus body and footers, and checks any message you paste against the 1.0.0 spec.

Runs in your browser. What you type stays on this page. By Jake Marsh. Checked against Conventional Commits 1.0.0 specification on 2026-11-16.

feat and fix are the two the spec defines. The rest are common conventions.
A noun for the part of the codebase, like parser or api.
One short line, imperative, no period. Describes what the commit does.
Why the change was made. Starts one blank line after the description.
Breaking change
Explain what breaks and what to do. Also marks the commit as breaking.
One per line: Refs: #123, Reviewed-by: Z, Closes #45. Use - in place of spaces in the name.

No problems found.

Release effect with semantic versioning tools: Minor release.

Commit message

Copy it, or run: git commit -m 'feat(parser): add ability to parse arrays'

feat(parser): add ability to parse arrays

How to use it

  1. Pick a type. Use feat for a new feature and fix for a bug fix, or one of the others for work that does not change behavior.
  2. Add a scope if the change sits in one part of the codebase, then write the description as a short imperative line with no period.
  3. Add a body for the why, and footers such as Refs: #123 if you need them.
  4. For a breaking change, tick the ! box, add a BREAKING CHANGE note, or both.
  5. Copy the message or download it, then commit with git commit -F. To test a message you already wrote, switch to Check a message.

How a message is laid out

<type>[optional scope][!]: <description>

[optional body]

[optional footer(s)]
The structure from the spec
  • feat adds a feature and maps to a minor version in semantic versioning. fix patches a bug and maps to a patch version.
  • A breaking change, marked with ! or a BREAKING CHANGE: footer, maps to a major version whatever the type is.
  • Footers follow git trailer style: a token with dashes instead of spaces, then ": " or " #", then a value. BREAKING CHANGE is the one token that may contain a space.
  • Types besides feat and fix are allowed. The spec gives them no release meaning unless the commit is breaking.

What the checker flags

Errors are things the spec requires: a type, a colon and a space, a non-empty description, a blank line before the body, and a description on any BREAKING CHANGE footer.

Warnings are habits that make history easier to read: a first line over 72 characters, a trailing period, a capitalized or past-tense description, an unusual type, or a lowercase "breaking change:" that tools will not recognize.

Questions

Is the scope required?
No. The scope is optional. When you use one, it goes in parentheses right after the type and should be a noun for a section of the codebase, such as fix(parser):.
What is the difference between ! and a BREAKING CHANGE footer?
Both mark a breaking change. The ! sits before the colon and is easy to spot in git log. The footer carries the explanation. You can use either or both.
Which types can I use?
The spec only defines feat and fix. It points to @commitlint/config-conventional, based on the Angular convention, which adds build, chore, ci, docs, style, refactor, perf and test. Any other noun is valid, but release tools give it no version bump unless the commit is breaking.
Should the description be capitalized?
The spec does not say. Its examples start in lowercase with no trailing period, and commitlint's conventional config rejects sentence case by default. The checker warns about a capital letter rather than rejecting it.
How do I commit a message with a body?
Download the file or paste it into a file, then run git commit -F commit-message.txt. Passing a multi-line message to -m on the command line works too, but quoting gets awkward.
Does the page send my commit message anywhere?
No. Building and checking happen in your browser and nothing is uploaded.

Sources

Checked 2026-11-16.

Keep the work behind each commit on one list.

Taskhold gives you and your coding agents one task list: each agent files its steps, reports progress and asks its questions where you can answer from your phone. Agents that write these commits can see what is done and what is next. Try the live board with no account.

Or connect your agent first, no sign-up: add https://taskhold.com/api/mcp as an MCP server. The first time it uses Taskhold, it gives you the trial link.

Related tools

  • CLAUDE.md and AGENTS.md generator

    Answer a few questions about your repo (stack, commands, rules, do-nots) and get a starter CLAUDE.md and AGENTS.md, either as one shared file or as two.

  • TODO comment extractor

    Paste code or drop a folder and get every TODO, FIXME, HACK, XXX and BUG comment with its file and line, as a checklist, JSON or CSV.

  • Claude Code permissions builder

    Pick what Claude Code may run, what it must ask about and what it can never touch, and get the allow, ask and deny block for settings.json. Paste an existing file to check it.

All free tools