Smithers Jev Workflows
Smithers uses Jev checks and scores across repository and workflow automation.
Smithers uses Jev checks and scores across repository and workflow automation.
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.
Which act that Smithers cannot perform does this message ask for? Answer `none` unless the message plainly asks for one of them.
Selected user message plus prior conversation and repository context. This fixed classifier identifies a message asking for an act the product cannot perform.
Use the configured repository check scope to identify which maintainer rule applies.
Split the validated diff into file path, first changed line, and bounded hunk text.
Batch one typed violation judgment per hunk against the rule text.
Classify clear violations and clear non-violations; preserve intermediate answers as uncertain and fail on unavailable evaluation.
The decision is scoped to a single rule and changed hunk, and the implementation preserves uncertainty as a distinct check result.