Commit Check

"No LLM bots in Co-authored-by": checking the rule before the squash merge

2026-10-24T00:00:00+00:00

"No LLM bots in Co-authored-by": checking the rule before the squash merge¶

Some projects have written down a short, strict rule about AI tools. The AI policy that pip and attrs use puts it in one line:

No LLM bots in Co-authored-by:s.

A pull request that lists an LLM product as a co-author "can't be merged and will be closed without further discussion". Using AI tools is still allowed, but contributors "must remove any LLM co-author tags and take full ownership of every line."

A machine can check that rule. Unless one does, a reviewer has to open every commit of every pull request and read its trailers.

Your AI agent signs your commits. Does your project have a policy for that?

2026-10-11T00:00:00+00:00

Your AI agent signs your commits. Does your project have a policy for that?¶

Ask Claude Code or Cursor to commit for you and, by default, the commit comes out stamped:

fix: resolve race condition in the cache

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Whether that line belongs in your history is a policy question, and open source has already given three different answers.

AI Attribution Governance: Enforcing AI Disclosure Policies at the CI Level

2026-07-06T00:00:00+00:00

AI Attribution Governance: Enforcing AI Disclosure Policies at the CI Level¶

The open-source ecosystem is converging on a hard question: when a commit is written with AI assistance, how do we know — and how do we enforce the disclosure policy?

Python's discourse, Linux kernel's Assisted-by trailer, Fedora's AI policy, Apache's disclosure guidelines — every major project is grappling with this. But until now, there has been no tool at the CI level to enforce whatever policy a project chooses.

Commit Check v2.11.0 introduces AI Attribution Governance — a new feature that detects known AI tool signatures in commit messages and lets projects decide whether to forbid them outright. To our knowledge, no existing tool enforces this kind of policy at the CI level.

AI-native: JSON output and a Python API

2026-06-21T00:00:00+00:00

AI-native: JSON output and a Python API¶

More and more commits are written — or at least drafted — by AI agents and automation. So Commit Check is also built for machines — not just humans reading terminal output. This post covers the two features that make that possible: machine-readable JSON output and an import-friendly Python API.

From zero-config to org-wide policy

2026-06-21T00:00:00+00:00

From zero-config to org-wide policy¶

Commit Check works the moment you install it, but its real strength shows up when you start shaping the policy to fit your team. This post covers everything from the default behavior to organization-wide shared configuration.

One policy file for your Git history

2026-06-21T00:00:00+00:00

One policy file for your Git history¶

Most teams have a wiki page titled something like "How we write commit messages." It covers commit conventions, branch naming, sign-offs, and author email consistency — and then nobody reads it.

Commit Check exists to turn that wiki page into something Git actually enforces.