Commit Check CLI
Commit policy as code: validates messages, branches, authors and AI attribution from one cchk.toml in hooks and CI.
- 98 ★ on the repository
- Last commit
- MIT
Minimal access
Why this level
- Reads commit messages, branch names and file lists and with `--fix` edits the commit message text
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/commit-checkDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewMinimal accessThe tool runs nothing and makes no network calls.
- Reads commit messages, branch names and file lists and with `--fix` edits the commit message text
This is third-party code. Review the repository files before installing.
What it does
Commit Check validates commit messages, branch names, authors, sign-offs, tags, committed files and AI attribution against a single `cchk.toml`. It runs in the commit hook, in CI, on every pull request and inside an agent. With no config it checks Conventional Commits and Conventional Branch, and when the fix is obvious it hands you the line. With `--fix` the pre-commit hook corrects mechanical slips itself: a type's case, a missing colon. For agents there is the `commit-check` skill in the Agent Skills format, `--format json` output, a Python API and an MCP server. The skill teaches an agent to read `cchk.toml`, check a message before committing, follow the AI attribution policy and never skip the hook. For GitHub there is an app that adds a check run to every push.
Who it is for. Teams that want uniform commit and branch rules and control human and agent commits with one config.
Good fit when
- Agents write commits with arbitrary messages while the team needs Conventional Commits.
- Commits made with AI help must be labeled in an `agent/model` pattern and the label checked.
- Branch name checks and a ban on force pushes are needed.
- You want the check in pre-commit, GitHub Actions and the app with no separate workflow.
Not a fit when
- The project needs no commit rules: the tool would only add friction.
- You need automatic releases with versions: Commit Check only validates and cuts no releases.
- Python 3.11 is missing and the `commit-check` package cannot be installed.
Example request
Check my latest commit message with commit-check and fix it per the repository rules.Limitations
Python 3.11 or newer is required. Rules come from a single `cchk.toml`, and the defaults check only Conventional Commits and Conventional Branch. The GitHub App is free for public repositories and personal accounts, for others see the project site. The `--fix` autofix changes only mechanical slips and never rewrites the meaning of a message. The agent skill is installed separately with `npx skills add` and does not replace the hook: the agent has to follow it. The MCP server lives in a separate repository, `commit-check-mcp`.
How to disable. Remove the hooks from `.pre-commit-config.yaml`, the GitHub Actions step and the GitHub App, and uninstall the package with `pip uninstall commit-check`. Delete the skill folder from the agent directory.
FAQ
Is setup needed to start?
No. With no config Conventional Commits and Conventional Branch are checked, and rules are tuned later in `cchk.toml`.
How do I add it to pre-commit?
Add the `commit-check/commit-check` repository and the `check-message` and `check-branch` hooks to `.pre-commit-config.yaml`. With `args: [--fix]` the hook fixes slips itself.
How are AI labels checked?
The `commit.ai_disclosure_pattern` option sets a regex for the label value, for example `^\S+/\S+` for the `agent/model` format.
Which agents does the skill support?
The Agent Skills format is loaded by Claude Code, GitHub Copilot, Codex, Cursor and others. Install with `npx skills add https://github.com/commit-check/commit-check --skill commit-check`.
Where else does it run?
In GitHub Actions, in the GitHub App, from the Python API and through the MCP server. All use the same `cchk.toml`.
Discussion
No questions or reviews yet.
Related
CLI toolsaicommit2 writes commit messages for Git, YADM and Jujutsu from the diff via several AIs at once and lets you pick the best
Conventional Commit Message skill for agents
Conventional Commit Message
A skill that writes Conventional Commits messages: picks the type by release impact, the scope by package and checks the text with commitlint
A plugin makes the agent explain its code and, before a push, ask questions so you understand what you are merging.
A linter for the agent harness checks a repository's AGENTS.md, CLAUDE.md, CI and hooks and scores six dimensions.
A terminal diff viewer: all files in one stream, and an agent with the hunk-review skill walks through the changes and leaves line comments
A CLI that splits changes into atomic commits and writes conventional commit messages through an LLM, plus a skill for agents.
README in short
The README shows a quick start, pre-commit setup, a table of where it runs, `cchk.toml` options and a section on the agent skill. Rules and guides are on the site.