GeezerVison

Commit policy as code for teams and AI agents.

Catch bad commits before they merge — one config file, from your commit hook to every pull request.

✖ Commit rejected by Commit Check · 1 check failed

✖ CC001 message failed: updated the parser
  The commit message should follow Conventional Commits. See https://www.conventionalcommits.org
  Suggest: Use <type>(<scope>): <description>, where <type> is one of: feat, fix, docs, style, refactor, test, chore, perf, build, ci
  Docs:    https://commit-check.com/rules/#cc001

Every failure names a stable rule ID, the value that failed, what to do about it, and where it is documented — as text, JSON, a job summary, a PR comment, or an MCP tool call.

                      cchk.toml
                          │
        ┌─────────────────┼─────────────────┬─────────────────┐
        ▼                 ▼                 ▼                 ▼
  your machine       pre-commit         GitHub App        AI agents
 (commit-check)         hook            or Action           (MCP)
        │                 │                 │                 │
        └─────────────────┴────────┬────────┴─────────────────┘
                                   ▼
                       same rules, same verdict

Write the rules once. Every surface reads that same file, so a commit that passes on a laptop passes in CI — and an agent asking "would this message be accepted?" gets the answer your maintainers actually configured.

Nothing to configure to begin with: the defaults enforce Conventional Commits, Conventional Branch, and sane subject lengths.

On GitHub, the quickest start is the Commit Check App. Install it on your organization or account, and every push to a branch and every pull request gets a check run, with no workflow file. It is free for public repositories and personal accounts.

To run the checks yourself instead:

# .pre-commit-config.yaml — feedback while the message is still being written
repos:
  - repo: https://github.com/commit-check/commit-check
    rev: v2.20.4
    hooks:
      - id: check-message
      - id: check-branch

# .github/workflows/commit-check.yml — where it becomes a policy, not a suggestion
- uses: commit-check/commit-check-action@v2
  with:
    message: true
    branch: true
    pr-title: true
    pr-comments: true  # needs permissions: pull-requests: write

Every rule and option is at commit-check.com.

• It reads commit metadata, not your code. It is not a linter.
• A pre-commit hook can be skipped with --no-verify, so only the CI check is really a policy — the hook is there to save you the round trip.
• Imperative-mood checking reads a word's form, so a subject led by a noun that looks like a gerund (fix: spelling in the docs) gets reported.

Commit metadata rules are usually behind a paid tier: GitHub's metadata restrictions need Enterprise, and Bitbucket's equivalent is Yet Another Commit Checker, a paid Marketplace app. Commit Check is the open alternative — and because the policy is a file in your repository rather than a settings page, it can be reviewed, diffed, and rolled back like anything else you version.

• 🔒 SLSA Level 3 build provenance — verify any release yourself with gh attestation verify <wheel> --repo commit-check/commit-check
• 🏢 Runs in repositories across Apache, FreeBSD, JUnit, Texas Instruments, Mila, and many more
• 📖 MIT licensed, actively maintained, and itself following Conventional Commits and Conventional Branch

Issues for bugs and feature requests · Discussions for questions and ideas · Docs for everything else.