Small decisions. Interesting possibilities.Submit contentSubmit
Smithers Jev Workflows preview

Smithers Jev Workflows

Smithers uses Jev checks and scores across repository and workflow automation.

Added to Jevfast

How it uses Jev

In Smithers’ repository checks, Jev judges each in-scope changed diff hunk against one maintainer rule using a boolean violation question. Code groups the answers into pass, fail, or uncertain outcomes using explicit probability bands; an unavailable judgment is an error rather than an invented verdict.

What Jev decides

Identify an unavailable act requested in the messageExample answers · not a recorded Jev response · Source ↗
Question 1 · impossible
YOUR APP
INSTRUCTION

Which act that Smithers cannot perform does this message ask for? Answer `none` unless the message plainly asks for one of them.

STATE

Selected user message plus prior conversation and repository context. This fixed classifier identifies a message asking for an act the product cannot perform.

JEV · CHOICE
  1. none
  2. email
  3. local-files
  4. messaging
  5. push
  6. pr

App workflow

  1. Select an in-scope rule

    Use the configured repository check scope to identify which maintainer rule applies.

  2. Extract changed hunks

    Split the validated diff into file path, first changed line, and bounded hunk text.

  3. Evaluate each hunk

    Batch one typed violation judgment per hunk against the rule text.

  4. Apply probability bands

    Classify clear violations and clear non-violations; preserve intermediate answers as uncertain and fail on unavailable evaluation.

Why it is interesting

The decision is scoped to a single rule and changed hunk, and the implementation preserves uncertainty as a distinct check result.