# Commit Check

> Commit policy as code for teams and AI agents: commit message, branch naming, author and sign-off standards in one config file, enforced in hooks, CI and pull requests.

## Pages

- [Home](https://commit-check.com/index.md): Commit policy as code for teams and AI agents. Messages, branches, authors and AI attribution, checked from your commit hook to every pull request.
- [Getting started](https://commit-check.com/getting-started.md)
- [Where to run it](https://commit-check.com/guides/integrations.md)

## Guides

- [Pre-commit hook](https://commit-check.com/guides/pre-commit.md)
- [GitHub Action](https://commit-check.com/guides/github-actions.md)
- [GitHub App](https://commit-check.com/guides/github-app.md)
- [GitLab, Bitbucket, Azure](https://commit-check.com/guides/other-ci.md)
- [With release tools](https://commit-check.com/guides/release-tools.md)
- [With AI coding agents](https://commit-check.com/guides/ai-agents.md)
- [Across an organization](https://commit-check.com/guides/organization.md)
- [MCP server](https://commit-check.com/guides/mcp.md)
- [Python API](https://commit-check.com/guides/python-api.md)
- [Policy guides](https://commit-check.com/guides/policies.md)
- [Command-line recipes](https://commit-check.com/example.md)
- [Troubleshooting](https://commit-check.com/troubleshoot.md)
- [Migrating from v1](https://commit-check.com/migration.md)

## Reference

- [Rules](https://commit-check.com/rules.md)
- [Configuration](https://commit-check.com/configuration.md)
- [Changelog](https://commit-check.com/changelog.md)
- [Privacy](https://commit-check.com/privacy.md)
- [Terms of Service](https://commit-check.com/terms.md)

## Compare

- [GitHub's built-in rules](https://commit-check.com/compare/github-rules.md)
- [Other tools](https://commit-check.com/compare/tools.md)

## Blog

- [Blog](https://commit-check.com/blog/index.md)

## Other pages

- [AI-native: JSON output and a Python API](https://commit-check.com/blog/posts/2026-06-21-ai-native-json-output-and-a-python-api.md)
- [From zero-config to org-wide policy](https://commit-check.com/blog/posts/2026-06-21-from-zero-config-to-org-wide-policy.md)
- [One policy file for your Git history](https://commit-check.com/blog/posts/2026-06-21-one-policy-file-for-your-git-history.md)
- [AI Attribution Governance: Enforcing AI Disclosure Policies at the CI Level](https://commit-check.com/blog/posts/2026-07-06-ai-attribution-governance-enforcing-ai-disclosure-policies-at-the-ci-level.md)
- [Your AI agent signs your commits. Does your project have a policy for that?](https://commit-check.com/blog/posts/2026-10-11-ai-commit-attribution-policy.md): AI coding agents stamp their own trailers on your commits. Open source has answered that three ways; here is how to enforce whichever one your project chose, on every commit.
- ["No LLM bots in Co-authored-by": checking the rule before the squash merge](https://commit-check.com/blog/posts/2026-10-24-no-llm-co-authors.md): Some projects close any pull request that credits an LLM as a co-author. Here is how to check that rule on every pull request, including the co-author lines a squash merge copies into main.
- [How eleven projects check AI attribution in CI](https://commit-check.com/blog/posts/2026-11-10-ai-attribution-checks-in-ci.md): I read the CI checks that eleven projects run on AI-assisted commits. The same trailer is required by one project and blocks the merge in another. Here is what each one checks, and what none of them can.