# Conventional commit checker

- Human page: https://happytails.ai/en/developer-tools/conventional-commit-checker/
- Markdown: https://happytails.ai/en/developer-tools/conventional-commit-checker.md
- Structured JSON: https://happytails.ai/agents/en/developer-tools/conventional-commit-checker/index.json
- Visibility: public

## Tool capabilities

| Property | Value |
| --- | --- |
| Tool ID | `conventional-commit-checker` |
| Category | developer-tools |
| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |
| Browser execution | Automatic updates after valid input or file selection. |
| Browser processing | Browser; see tool notes for network behavior. |
| HTTP API | Not callable through HTTP. |
| Browser-agent interface | run_current_tool |

### Implementation notes

Check one complete Conventional Commits 1.0 message. Scope and ! are optional; the body and footers need a blank separator. feat suggests minor, fix suggests patch, and ! or a BREAKING CHANGE footer suggests major. Other types are allowed. This is syntax and declared impact, not a review of the actual code or release policy. Runs on your device. No remote configuration, repository or credentials are queried. Up to 1,000,000 input characters; output files are limited to 4,000,000 characters each.

### Inputs and settings

Text input: Commit message.

Example or placeholder shown in the interface (not a validated fixture):

```text
feat(search): add saved filters

Allow users to reuse filter settings.

Refs #42
```

Paste text to process locally. Review the supported syntax and the result before downloading. Results update as you type. Up to 1,000,000 characters.

No additional settings are declared for this tool.

### Browser-agent workflow

1. Open the human page in a browser that supports WebMCP.
2. Discover the interface exposed by that page; use its actual schema.
3. Select files on the page first when the tool requires files.
4. Call `run_current_tool` with valid input and settings.
5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.

Calls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.

### Planning specification

Conventional Commits 1.0 structure and explicit impact rules. No repository access or automatic version bump. Runs on your device with no configuration, repository or credential lookups. Up to 1,000,000 input characters and 4,000,000 characters per output file.

This describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.

### Complete machine-readable capability record

```json
{
  "id": "conventional-commit-checker",
  "category": "developer-tools",
  "built": true,
  "requirements": "Conventional Commits 1.0 structure and explicit impact rules. No repository access or automatic version bump. Runs on your device with no configuration, repository or credential lookups. Up to 1,000,000 input characters and 4,000,000 characters per output file.",
  "implementation": {
    "fields": [],
    "live": true,
    "presentation": "metrics",
    "note": "Check one complete Conventional Commits 1.0 message. Scope and ! are optional; the body and footers need a blank separator. feat suggests minor, fix suggests patch, and ! or a BREAKING CHANGE footer suggests major. Other types are allowed. This is syntax and declared impact, not a review of the actual code or release policy. Runs on your device. No remote configuration, repository or credentials are queried. Up to 1,000,000 input characters; output files are limited to 4,000,000 characters each.",
    "experience": {
      "automatic": true,
      "single": false,
      "inputMaxLength": 1000000,
      "inputMode": "text",
      "label": "Commit message",
      "placeholder": "feat(search): add saved filters\n\nAllow users to reuse filter settings.\n\nRefs #42",
      "help": "Paste text to process locally. Review the supported syntax and the result before downloading. Results update as you type. Up to 1,000,000 characters.",
      "action": null
    },
    "mode": "automatic",
    "interactive": false
  },
  "execution": "Browser interface",
  "api": null,
  "browser_agent": {
    "supported": true,
    "name": "run_current_tool",
    "discovery": "WebMCP on the human page in a supporting browser",
    "verification": "See audit/API-AUDIT.md; availability is not verification"
  }
}
```

## Page guide

Check a Conventional Commit message and its declared release impact. Review header, body and breaking-change footer issues.

How can we improve this tool?

Report a problem or share an idea.

Please leave out private information. Your message and the tool name go to our team via PostHog.

### How to use Conventional commit checker

1. Paste one complete commit message.
2. Review format issues and the declared release impact.
3. Download the parsed report or use accepted messages in the changelog generator.

## Useful next steps

- [Changelog generator from commits](https://happytails.ai/en/developer-tools/changelog-generator-from-commits/) ([Markdown](https://happytails.ai/en/developer-tools/changelog-generator-from-commits.md))

## Check one complete commit message

Paste the header and any body or footers. The expected shape is type(scope)!: description, with scope and ! optional. A blank line separates the header from the body or footers. Custom types are allowed; this does not enforce a team-specific type allowlist.

### See the impact declared by the message

feat suggests a minor change, fix suggests a patch, and ! or a BREAKING CHANGE footer suggests a major change. A breaking-change footer takes precedence. Other types have no automatic version impact here.

### Review meaning before making a release

The tool checks message structure, not the code behind it. A commit can have valid syntax and still misdescribe its change. Project release rules, pre-1.0 policy and version selection remain a human decision. The downloadable report includes the parsed message you supplied.