Small decisions. Interesting possibilities.Submit contentSubmit
Jev Belay GIF preview

Jev Belay

A Claude Code Stop hook that reads the turn's transcript locally and spends one Jev call only when files changed without a passing check, so an unverified done claim is sent back to run the suite.

Added to Jevfast

How it uses Jev

The hook spends a request only when a turn changed files and no check has passed since. The state carries the task from the user's prompt, the final assistant message and a run summary with the file-change count and the check commands that ran with their pass or fail result. Four questions answer together: whether the message claims the work is done, whether it claims checks passed, whether running checks would apply, and a choice of complete, partial, blocked or other. Code blocks only above its 0.7 threshold with a decisive outcome pick.

What Jev decides

One Stop decision with four questions (illustrative)Example answers · not a recorded Jev response · Source ↗
Question 1 · claims done
YOUR APP
INSTRUCTION

Does the final message present the requested work as finished or working?

STATE

The state is the user's task, the final assistant message, and a run summary with the number of file changes and the check commands that ran and whether each passed. The transcript itself stays on the machine.

JEV · NOUL
YesNo
Question 2 · claims verified
YOUR APP
INSTRUCTION

Does the final message claim that tests, a build or other checks were run and passed?

STATE

The state is the user's task, the final assistant message, and a run summary with the number of file changes and the check commands that ran and whether each passed. The transcript itself stays on the machine.

JEV · NOUL
YesNo
Question 3 · verification applies
YOUR APP
INSTRUCTION

Would running the project's tests, build or lint be a meaningful way to check the work the task asks for?

STATE

The state is the user's task, the final assistant message, and a run summary with the number of file changes and the check commands that ran and whether each passed. The transcript itself stays on the machine.

JEV · NOUL
YesNo
Question 4 · outcome
YOUR APP
INSTRUCTION

What does the final message report about the task?

STATE

The state is the user's task, the final assistant message, and a run summary with the number of file changes and the check commands that ran and whether each passed. The transcript itself stays on the machine.

JEV · CHOICE
  1. complete
  2. partial
  3. blocked
  4. other

App workflow

  1. Catch the stop

    The Stop hook runs when Claude Code is about to end a turn and reads the session transcript locally.

  2. Skip the cheap cases

    With no file changes, or with a passing check after the last change, the turn ends without any model call.

  3. Ask one request

    The task, final message and run summary become the state for the four questions, with a bounded timeout.

  4. Block or allow

    A confident done or verified claim without a passing check sends the turn back with the reason, and any error or low confidence lets it end.

Why it is interesting

A clean run costs nothing because the local transcript already proves it, so the paid question is spent only where a false completion claim is possible. Presence of a passing check is evidence and absence of one is not, which is why the hook asks whether checks would even apply instead of treating silence as failure.