DevOps Generators

Commit Validator

All tools

Find out instantly whether a commit subject would pass a Conventional Commits check.

How it works

Four simple steps

1

Paste the message

Add the full commit message or just its subject line.

2

Check the subject

The first line is tested against the pattern as you type.

3

Read the result

A pass echoes the subject; a failure shows an error message.

4

Reword and retry

Fix the type, scope or length until the line passes.

Commit Validator

About Commit Validator

A pull request fails because one commit out of twelve has a subject the commit lint step dislikes, and the error is vague. Paste the message here to see whether its first line matches the expected pattern before you reword it.

Only the first line is checked. It must start with one of ten lowercase types (feat, fix, docs, style, refactor, perf, test, chore, build or ci), optionally followed by a scope in parentheses and an exclamation mark for breaking changes, then a colon, one space and a description of 1 to 72 characters. A passing subject is echoed back under Valid subject; anything else shows an error. The check reruns on every keystroke.

The rules are stricter than the specification in places. Scopes may only contain letters, digits, underscores and hyphens, so ui/button or deps.dev fail. revert is not an accepted type, and Feat with a capital letter fails. The 72-character cap applies to the description after the colon, not the whole line. If your team runs commitlint with its own config, that config wins; use this as a first pass. To experiment with a custom rule, paste the pattern into the regex tester.

Messages are checked locally in the page. Building a subject from scratch is easier in the Conventional Commit generator, and the Git branching guide shows where commits fit in a team workflow.

Keyboard shortcut

Ctrl Enter - Run tool
FAQ

Frequently asked questions

See all FAQs

Answers for this tool. For site-wide help, open the FAQ hub.

The validator accepts ten types and revert is not among them. If your project allows reverts, treat that failure as expected or check the message against your own commitlint config.

Scopes are limited to letters, digits, underscores and hyphens. A slash, dot, comma or space inside the parentheses makes the line fail even though some tools accept them.

View more FAQs

Related tools

View all

Kubernetes Manifest Studio

Generate Deployment, Service, and Ingress YAML with a drift checklist.

Open

K8s Inspector

Summarize Kubernetes YAML kinds, names, and labels.

Open

K8s Resource Diff

Diff two Kubernetes manifests locally.

Open

K8s Manifest Splitter

Split multi-document YAML into one file per resource.

Open

Explore 321 free tools

Everything you need as a developer, marketer or creator - in one beautiful place.

Browse all tools