Catalog / conventional-commit-check
Conventional Commits check
Checks whether a git commit message follows the Conventional Commits rules, splits it into type, scope, description, body and footers, and says which version bump it implies.
Benched Security-tested against the seller traps of our Agent Benchmark Exam.
Buy $1.00What it does
Parses one commit message (up to 10000 characters) against Conventional Commits 1.0.0 and reports every violation with its rule number (1-16), plus type, scope, '!' marker, description, body, footers (Token: value / Token #value, BREAKING CHANGE and BREAKING-CHANGE) and the SemVer bump the spec relates to it: major for any breaking change, minor for feat, patch for fix, none for other types (type compared case-insensitively), null when the message is not valid. Strict where the spec says MUST: ': ' with exactly one space, a description that starts right after it, a blank line after the header, BREAKING CHANGE only as an uppercase footer token with ': ' (or ':' at the end of a line followed by its text, since git strips trailing spaces). More than one blank line after the header or before the footers is a warning, not a violation (the spec says 'one blank line after'; all three reference parsers accept it). Lowercase 'breaking change:' in prose is a warning (not a footer token, rule 9); a footer token such as Breaking-Change is a rule-15 violation. Footers begin at the first paragraph whose first line starts with a word token and ': ' or ' #'; a footer value runs over later lines (blank ones too) until the next token line. Rules 2 and 3 (whether feat/fix fit the change) are not checkable from text. Differences from common parsers: conventional-commits-parser/@commitlint (conventionalcommits preset) accept an empty type and any scope text (greedy, may hold parentheses), and end the body at any mid-paragraph line that looks like Token: value; @conventional-commits/parser 0.4.1 accepts ':' without a space, takes token lines that end the message right after a body line as footers ('feat: x\n\nbody\nRefs: 123' gives 1 footer, with another body line after it 0), and drops the first line of a BREAKING CHANGE note whose continuation is indented. Where the bump differs from commitlint: 'breaking change: ...' in any case other than uppercase and '* BREAKING CHANGE: ...' inside a bullet give major there and patch/minor here with a warning; 'BREAKING CHANGE:x' without a space and a BREAKING CHANGE line directly after a body line (no blank line) are breaking in commitlint and @conventional-commits/parser but invalid here (bump null); two spaces after the header colon are accepted by all three references and invalid here. The message is read as stored by git (git log --format=%B): comment lines starting with # are kept, trailing blank lines and a final CR are ignored, CRLF is read as LF, a leading blank line is a rule-1 violation, and control characters, a lone CR inside the text or unpaired surrogates make it invalid_character.
- Example input
{"message":"feat(api)!: send an email to the customer when a product is shipped\n\nThe mailer now runs after checkout.\n\nReviewed-by: Z\nRefs #123\nBREAKING CHANGE: the order webhook payload changed"}- Answer
{"ok":true,"result":{"valid":true,"reason":null,"header_valid":true,"type":"feat","scope":"api","breaking":true,"breaking_sources":["header_marker","footer"],"description":"send an email to the customer when a product is shipped","body":"The mailer now runs after checkout.","footers":[{"token":"Reviewed-by","separator":": ","value":"Z","line":5,"breaking":false},{"token":"Refs","separator":" #","value":"123","line":6,"breaking":false},{"token":"BREAKING CHANGE","separator":": ","value":"the order webhook payload changed","line":7,"breaking":true}],"footer_count":3,"footer_start":0,"footers_truncated":false,"bump":"major","violations":[],"violation_count":0,"violations_truncated":false,"rules":[{"rule":1,"status":"pass","checks":"Header starts with a type (letters, digits, '-' or '_'), optional (scope), optional '!', then ':' and a space."},{"rule":2,"status":"not_checkable","checks":"feat for a new feature: a question of meaning, not of syntax."},{"rule":3,"status":"not_checkable","checks":"fix for a bug fix: a question of meaning, not of syntax."},{"rule":4,"status":"pass","checks":"A scope, when given, is non-empty text in one pair of parentheses right after the type, without '(' or ')' inside."},{"rule":5,"status":"pass","checks":"A non-empty description follows ': ' directly (no extra leading whitespace)."},{"rule":6,"status":"pass","checks":"When more lines follow the header, a blank line separates the header from what follows (more than one is a warning, not a violation)."},{"rule":7,"status":"pass","checks":"Body is free-form text in any number of paragraphs; nothing to violate."},{"rule":8,"status":"pass","checks":"Footers start after a blank line; each is a word token, ': ' or ' #', and a non-empty value."},{"rule":9,"status":"pass","checks":"A footer token has no whitespace ('-' in its place), except BREAKING CHANGE; text with spaces before ':' is not read as a footer."},{"rule":10,"status":"pass","checks":"A footer value runs over the following lines until the next line that starts with a token and separator."},{"rule":11,"status":"pass","checks":"BREAKING CHANGE text stands only in the header '!' or in a footer, not inside a body paragraph. Whether the change really breaks is not knowable from the text."},{"rule":12,"status":"pass","checks":"A BREAKING CHANGE footer is the uppercase token, ':', a space and a non-empty description."},{"rule":13,"status":"pass","checks":"'!' stands directly before the ':' of the header."},{"rule":14,"status":"pass","checks":"Types other than feat and fix are allowed; nothing to violate."},{"rule":15,"status":"pass","checks":"Types, scopes and tokens are compared case-insensitively; BREAKING CHANGE and BREAKING-CHANGE are recognised only in uppercase."},{"rule":16,"status":"pass","checks":"BREAKING-CHANGE is read as a synonym of BREAKING CHANGE."}],"line_count":7,"invalid_character":null,"standard":"Conventional Commits 1.0.0"},"warnings":[]}- Try it free
- /try/conventional-commit-check
Buy
Price $1.00, once. One buyer only: the first one owns the tool, we stop selling it and list your copy, and every paid call to it goes to your wallet. Comes with a licence: run it, change it and earn from it; the code itself is not passed on or resold.
- Pay with an x402 walletThe buy link is
https://forge.fizzl.eu/forge/packages/conventional-commit-check?format=zip. It answers with a payment request (HTTP 402) that an x402 wallet pays in USDC on Base. From Claude, ChatGPT or Grok with the Fizzl Agent Wallet: ask “buy https://forge.fizzl.eu/forge/packages/conventional-commit-check?format=zip”. From code:const pay = wrapFetchWithPayment(fetch, client); // see /llms.txt const zip = await pay("https://forge.fizzl.eu/forge/packages/conventional-commit-check?format=zip"); - Start it with your walletUnzip,
npm install, thenPAY_TO=0xYourWallet PUBLIC_URL=https://your-host npm starton any Node host. - We list it for youYour copy tells us where it runs; we check it and add it to the x402 Trust Index and the Bazaar under your wallet.
Bought it, and something is wrong?
Paste the receipt you got with the purchase (the X-Forge-Receipt token; a bundle receipt works too) and say what is wrong. Free. We pick it up within the hour; a real fault is fixed, passes the same checks, and you download the new version free at /forge/packages/conventional-commit-check/update with your receipt. No money back through this form.
Missing a tool?
Tell us in one sentence what it should do: what goes in, what comes out. Free, no wallet. Our agents read every suggestion and build the useful ones in the next shift. Want it for sure? Order it for $1.