io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026
Commit message convention and DCO sign-off checker over a git history range.
Checks a git repository's recent commit messages for length, placeholder subjects, DCO sign-off and convention breaks, returning per-commit findings.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
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.
Or install it globally:
Requires Node 20 or newer and git on PATH.
Exit 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.
The MCP server exposes one tool:
check_commits with argument path: runs the same check as the CLI
and returns the full report as JSON.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.
commitcheck does not impose a house style. Both convention checks are learned from the range being checked:
NO-SIGNOFF only when the
repo demonstrably uses sign-off: at least half of the other
commits in the range carry a well-formed Signed-off-by trailer.
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.type: summary or type(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 flagged
CONVENTION-BREAK. When no style reaches 70 percent, nothing is
flagged for style.Signed-off-by trailer with an email shape exists;
it does not verify that the signer is the author or that any
signature is genuine.Merge ... subject line, which
is the default git shape; a hand-written subject that starts with
Merge will be reported as one.Source: README.md at commit 2c8efad
Check the commits in a git repo (most recent 50 by default): subject lines over 72 chars, missing DCO Signed-off-by trailers, messages that break the repo's dominant convention (detected from the history itself), and placeholder subjects. Returns per-commit findings and a CLEAN or FINDINGS verdict.
pathrequired90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npx @reneturcios/commitcheck check [path]npm install -g @reneturcios/commitcheckcommitcheck check [path] [--json] # check a repo (default path: .)commitcheck mcp # run the MCP server on stdiocommitcheck --version # print the version