commitcheck
Checks a git repository's recent commit history for hygiene issues, including subject length, placeholder subjects, DCO Signed-off-by trailers, malformed trailers, and message convention breaks, returning findings with rule names and commit short SHAs.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
commitcheck
Commit hygiene checker for a git repository's recent history. It reads
the most recent 50 commits and checks subject length, placeholder
subjects, DCO Signed-off-by trailers, malformed trailers, and whether
each commit follows the message convention the repo itself actually
uses. Every finding names the rule and the short sha of the commit it
came from.
Install
npx @reneturcios/commitcheck check [path]Or install it globally:
npm install -g @reneturcios/commitcheckRequires Node 20 or newer and git on PATH.
Related MCP server: Charlie Work
CLI
commitcheck check [path] [--json] # check a repo (default path: .)
commitcheck mcp # run the MCP server on stdio
commitcheck --version # print the versionExit codes: 0 when the verdict is CLEAN, 1 when it is FINDINGS,
2 for a usage error or an unreadable target, and 141 when the
reader closed the output pipe early (the shell-visible equivalent of
death by SIGPIPE).
Findings are printed in git log order, newest first, and the order is deterministic for a given history.
MCP
The MCP server exposes one tool:
check_commitswith argumentpath: runs the same check as the CLI and returns the full report as JSON.
Rules
Rule | Severity | What it means |
| medium | The subject line is over 72 characters. |
| low | The subject is empty or a placeholder such as |
| medium | The commit has no |
| low | The subject breaks the dominant message style of the range (see below). |
| info | A merge commit, reported for context. Merge commits are never a finding above info. |
| low | A |
The verdict is CLEAN when the range has no medium findings, and FINDINGS otherwise. Low and info findings are reported but do not change the verdict.
The adaptive rules, stated plainly
commitcheck does not impose a house style. Both convention checks are learned from the range being checked:
DCO / sign-off. A commit is flagged
NO-SIGNOFFonly when the repo demonstrably uses sign-off: at least half of the other commits in the range carry a well-formedSigned-off-bytrailer. If the repo does not use sign-off, no commit is flagged for missing it. A malformed sign-off line does not count as a sign-off.Message convention. Two styles are tracked: conventional subjects (
type: summaryortype(scope): summary) and capitalized imperative subjects (Add the thing). When one style is used by at least 70 percent of the non-merge commits in the range, it is the dominant style, and a commit that breaks it is flaggedCONVENTION-BREAK. When no style reaches 70 percent, nothing is flagged for style.
Limits
Only the last 50 commits are checked.
Style detection is statistical. A short or mixed history may have no dominant style, in which case no convention findings are produced.
Sign-off presence is checked, not signature validity. commitcheck verifies that a
Signed-off-bytrailer with an email shape exists; it does not verify that the signer is the author or that any signature is genuine.Merge commits are detected from the
Merge ...subject line, which is the default git shape; a hand-written subject that starts withMergewill be reported as one.
This server cannot be deployed
Maintenance
Related MCP Connectors
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and security.
Read-only scan of a public GitHub repo for leaked secrets, with a 0-100 grade.
Your coding agent asks the business logic of your repository and checks commits before they land
Evaluates any GitHub repository for license risk, maintenance velocity, stars/forks, and supply-c.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables scanning projects for dependency vulnerabilities, secrets, license conflicts, code quality, and git health, returning a 0-100 health score with actionable suggestions.4 npmMIT
- AlicenseAqualityCmaintenanceScans a repository for maintenance toil (flaky tests, expiring certificates, TODO rot, dead flags, etc.) and returns a prioritized queue with a credit ledger to track who cleared what.71MIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients to run deterministic, read-only local repository audits for risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration, returning structured findings without sending source code to a service.63 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables an agent to check a repository's contribution rules (AI policy, CLA/DCO, assignment and claim windows) and an issue's status (linked open, merged and closed PRs, active claims, merge friendliness) before writing any code. It returns a go, comment & claim first, or don't verdict with the rule or PR evidence behind each reason, reading only and never opening PRs or posting comments.MIT