Jev commit message specificity

Jev commit message specificity. Does the message name a change?

Separate a checkable description from filler before reviewing whether the diff supports it.

Does this message say what changed?Live API
Try an example

Names both the changed behavior and its location.

Source: Background discussion on X

Source and example scope

These six synthetic inputs and Choice rules are original demonstrations. The API-collected X post links to jev-commit, whose pinned README describes related checks using Noul questions. This page is not that hook, does not execute Git, and does not reproduce its measurements or credential-blocking policy.

Judge the commit message wording only.

Decision rules and labels
CheckableFillerAmbiguousNeed evidence
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

Specific wording gives a reviewer something to verify.

A message such as wip records activity without naming a change. Reject empty email addresses names behavior and a location. This check distinguishes those cases before any claim is compared with code.

Specificity does not prove correctness. The timeout example states a checkable claim while its supplied diff says the opposite. It still belongs under Checkable here; the separate diff-support task handles that contradiction.

Use the label to request a clearer description. The demonstration does not generate replacement text, inspect a repository or create a commit.

These six synthetic inputs and Choice rules are original demonstrations. The API-collected X post links to jev-commit, whose pinned README describes related checks using Noul questions. This page is not that hook, does not execute Git, and does not reproduce its measurements or credential-blocking policy.

Conceptual illustration of supplied evidence entering a typed decision contract.
Shared conceptual illustration of the input contract; not a screenshot or measured performance result.
How it works

Run commit message specificity in four steps.

Supply a small, complete input, run the decision and inspect its recorded evidence.

  1. Illustration of adding the text or evidence for a decision

    Supply the evidence

    Enter the commit message. Optional diff context can illustrate a boundary, but this rule judges the wording of the message.

  2. Illustration of defining a question and its allowed choices

    Read the allowed outcomes

    The decision rule and the choice labels are sent with the evidence. Keep specificity separate from truth, length and completeness.

  3. Illustration of sending one input and comparing the returned choices

    Run and inspect the distribution

    The window makes a fresh server-side API request. It displays the highest-probability label, elapsed request time and estimated token cost. A provider failure produces an error, not a missing-evidence label.

  4. Illustration of reviewing a result and an uncertain item before using it

    Replay a pending local result

    Attach the label to a pending message-review note. A reviewer decides whether a rewrite is useful. Download the requests and saved observations. The offline consumer validates their hashes and prints a pending packet without executing it.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Specific fixCheckable100%
Bare progressFiller100%
Short but specificCheckable100%
Unclear objectAmbiguous100%
Specific but contradictedCheckable100%
Missing messageNeed evidence100%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Worked example

Replay the exact requests

Replay the saved synthetic requests and compare each observed label with its authored expectation. Any disagreement stays visible; the model is not rerun to obtain a preferred answer.

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Sample requests and authored expectations

Saved API observations

Single-request SDK runner

Offline preview consumer

Compare other decision examples

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Finding commit messages that contain only progress labels
  • Separating concrete wording from unsupported truth claims
  • Preparing a message for a later diff-support review

Outside this demonstration

  • Proving a message agrees with the staged code
  • Measuring coverage of every changed file
  • Automatically rewriting or approving a commit
Example FAQ

Questions about commit message specificity.

Input scope and downstream handling determine what the label can tell you.

Does a short message count as filler?

Length alone does not decide it. Remove the legacy CSV export endpoint states a checkable change in one sentence.

Why can a false claim receive Checkable?

This rule measures how specific the claim is. Compare it with the actual diff in the separate support check before relying on it.

Is the leading probability an accuracy measurement?

No. It is the distribution for this request. Six synthetic fixtures check the workflow and preserve disagreements; they are not a production benchmark.

What happens if the API request fails?

The window shows an error and returns no fresh judgment. The replay runner makes one request without retries. A missing-evidence label is about the input, not a substitute for an API failure.

Try your own commit message specificity input

Edit the supplied evidence above, or open the Playground for a different decision rule.