commit message

Status: ready — not yet trained.

Traits

Intent Clarity

Explains why the change was made ↔ Restates the diff or uses opaque shorthand

Whether the commit message explains the why behind the change — the motivation, context, or problem being solved — versus just restating what the diff shows or using opaque shorthand

Scope Precision

Single focused change with specific subject ↔ Bundled changes or generic subject

Whether the commit message addresses exactly one logical change with a specific subject, versus bundling unrelated changes or being so vague it could apply to any commit

Actionable Summary

Concise imperative subject line ↔ Fragment, question, or overlong subject

Whether the first line (subject) is a concise imperative sentence that lets a reader decide relevance without opening the diff — versus a fragment, a question, or a wall of text in the subject line

Context Sufficiency

Body provides context for future readers ↔ No body or body that adds nothing beyond the subject

Whether the commit body provides enough context for a future reader to understand the change without reading the code — linking to issues, explaining tradeoffs, noting what was considered and rejected — versus leaving the reader to guess from the diff alone

Signal Density

Every word carries information ↔ Filler phrases and content-free words

Whether every word in the message carries information — no filler phrases like "misc fixes", "some changes", "updated stuff" — versus padding, hedging, or content-free words that dilute the message

About

Scores the quality of a git commit message.

What it measures

Whether a commit message communicates its change effectively to future readers — reviewers doing git log, teammates bisecting a bug, or maintainers writing release notes months later. The model rewards messages that explain why a change was made (not just what the diff shows), stay focused on a single logical change, and provide enough context that you don't need to open the code to understand the commit's purpose. Filler like "misc fixes" or content-free subjects score low by design.

Feed the full commit message (subject + body) as input text.

Limitations

• Optimized for prose commit messages in English. Conventional Commit prefixes (feat:, fix:) are fine but not required or rewarded.
• Does not evaluate the code change itself — only the message.
• Very short messages (< 5 words) will reliably score low; that's intentional.

Pairs well with

• u22a8.changelog-entry — score the release notes these commits feed into
• u22a8.pr-description — the PR body that wraps the commits

Docs

• Tiers — categorical labels (Strong, Solid, Developing, Weak) assigned per trait
• Breaks — the per-trait trained boundaries between tiers