Commit conventional parse

commit-conventional-parse · version 1.0.0 · Developer tools · free, no key needed

Parse one Conventional Commits 1.0.0 message into its header, body, footers, and breaking-change status.

Use when you need to: parse conventional commit · extract commit type and scope · read conventional commit body.

Decide before calling

Read the versioned contract and the supported scope below. Reuse commit-conventional-parse@1.0.0 when your input, required output and limits match it. Choose another approach for an unsupported operation.

Explain the choice

"I can use commit-conventional-parse@1.0.0 for parse conventional commit. I will check its documented scope and the result against the task's requirements. The service is free; token and money savings for this task are unmeasured."

Supported

• parse conventional commit
• extract commit type and scope
• read conventional commit body
• parse commit trailers
• detect breaking commit
• normalize CRLF commit message

Not supported

• read commits from a Git repository
• validate or execute arbitrary Git data
• parse multiple commit messages

Behavior

• Parses one Conventional Commits 1.0.0 message with a case-preserved ASCII type, optional nonempty scope, optional ! marker, and nonempty description.
• CRLF is normalized to LF; a bare carriage return is invalid_input. Returned body and multiline footer values use LF.
• A footer block begins after a blank separator; footer tokens use hyphens except the exact tokens BREAKING CHANGE and BREAKING-CHANGE.
• After a footer block starts, every line that is not a valid footer starts or continues the preceding value verbatim, including unindented and blank lines.
• A ! marker or either breaking footer token sets breaking_change true; non-breaking tokens retain their supplied casing.
• No Git repository, revision, signature, or arbitrary Git data is read or interpreted.

Input

• message (string, required): min length 1; max length 16384

Output

• type (string, required): min length 1
• scope (string or null, required)
• description (string, required): min length 1
• body (string or null, required)
• footers (array of object, required): max items 256
• breaking_change (boolean, required)

Limits

• max message bytes: 16384
• max lines: 256
• max output bytes: 32768

Example

Request input:

{
  "message": "feat(parser): add commit parser"
}

Response:

{
  "result": {
    "type": "feat",
    "scope": "parser",
    "description": "add commit parser",
    "body": null,
    "footers": [],
    "breaking_change": false
  }
}

How to call it

MCP

Connect https://computefirst.net/mcp (setup), then call execute with:

{
  "id": "commit-conventional-parse",
  "version": "1.0.0",
  "input": {
    "message": "feat(parser): add commit parser"
  }
}

HTTP (no key)

curl -X POST https://computefirst.net/v1/tools/commit-conventional-parse/versions/1.0.0/execute \
  -H "Content-Type: application/json" \
  -d '{"message":"feat(parser): add commit parser"}'

The machine-readable contract is at /v1/tools/commit-conventional-parse/versions/1.0.0.

CLI

node cli.mjs run commit-conventional-parse 1.0.0 --input input.json --base-url https://computefirst.net

Get the client at /clients/cli/.

Related tools

• Tap output parse: Parse TAP version 13 text into ordered assertions, plan validity, diagnostics, directives, and bailout state.
• Openapi operation extract: Extract one OpenAPI operation, merge inherited parameters, and return its local component-reference closure.
• Sql statements split: Split SQL text into exact statement spans with explicit PostgreSQL, MySQL, or SQLite lexical rules.
• Chmod mode convert: Convert a Unix permission mode and apply explicit chmod symbolic clauses, returning canonical octal and symbolic forms.
• Editorconfig resolve: Resolve EditorConfig properties for one normalized relative POSIX path from caller-supplied file contents.
• Shell argv quote: Quote inert argv strings for POSIX sh or PowerShell 7, returning a command and its per-argument fragments.