Jev commit change coverage

Check whether a commit message covers the changes

Supply the message and complete change list. Check whether it describes all independent work, including supporting tests, or leaves part of the commit unexplained.

Does the description cover the supplied changes?Live API
Try an example

The message explicitly accounts for both changes.

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.

Compare the message with the supplied complete change list.

Decision rules and labels
CoveredUnmentioned workAmbiguousNeed 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

A true statement can describe only part of a commit.

The export message can be accurate while leaving out a new refund endpoint. This task checks coverage of the supplied change inventory rather than truth of an individual claim.

Coverage does not require a filename list. A regression test for the described bug can be clearly implied. An unrelated endpoint changes the scope and should be represented in the description.

The completeness flag matters. When changed files or hunks were omitted, the result cannot establish coverage of the whole commit. Supply the full inventory before interpreting the label.

In the recorded tests, Jev marked the implied regression test and the vague launch-cleanup description as Unmentioned work. The authored expectations were Covered and Ambiguous. Keep these disagreements visible when deciding how much human review this label needs.

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.

Illustration of checking a code change and reviewing a flagged line
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for commit change coverage.

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

    Add the information to check

    Supply the message and complete change list.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Covered, Unmentioned work, Ambiguous, Need evidence. Edit the choices only when testing your own rule.

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

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

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

    Review the next step

    Review Ambiguous, Need evidence before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Feature plus testsCovered100%
Unrelated endpointUnmentioned work100%
Implied supporting testUnmentioned work58.0%
Partial inventoryNeed evidence68.0%
Vague scope relationshipUnmentioned work51.0%
Explicitly broad coverageCovered83.0%

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. 4 of 6 results matched the authored fixture expectations. For Implied supporting test, the expectation was Covered; the observed choice was Unmentioned work. For Vague scope relationship, the expectation was Ambiguous; the observed choice was Unmentioned work.Verified

Understand the results

Source and example scope

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.

Using the result in your application

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.

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 independent work omitted from a message
  • Reviewing a message against a complete change inventory
  • Distinguishing supporting tests from an unrelated feature

Outside this demonstration

  • Proving the described implementation is correct
  • Inferring files omitted from the supplied inventory
  • Splitting commits or editing version-control history
Example FAQ

Questions about commit change coverage.

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

Must the message name every file?

No. The rubric accepts a change that is clearly implied, such as a regression test for the stated parser fix.

How does coverage differ from diff support?

Diff support asks whether one claim is established by code. Coverage starts from all supplied changes and asks whether the description accounts for them.

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 change coverage input

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