Small decisions. Interesting possibilities.Submit contentSubmit
Supercov preview

Supercov

Code quality and test coverage for coding agents: Jev scores each source file so the agent knows what to fix first.

Added to Jevfast

How it uses Jev

Supercov sends Jev questions about source-file properties and security checks. Its code validates the typed responses, then computes quality scores or reports flagged security surfaces; test coverage is measured separately.

What Jev decides

Check a source file for a long methodExample answers · not a recorded Jev response · Source ↗
Question 1 · long method
YOUR APP
INSTRUCTION

Does this file contain at least one method long enough that a reader cannot hold its steps in mind at once, and that visibly does several separable things? A long method that is one flat sequence of trivial statements does not count.

STATE

One source file: its path and complete source text. The selected Noul checks whether it contains a method too long to follow as one unit that also does separable things.

JEV · NOUL
YesNo

App workflow

  1. Discover source files

    Find eligible source files and prepare a request for each file or requested change.

  2. Ask bounded checks

    Send Jev the catalog or security questions for the source being assessed.

  3. Validate and compose results

    Validate response question IDs and typed answer bounds; compute quality scores in code or retain security findings without averaging.

  4. Combine with coverage

    Run the project’s existing test command and turn uncovered paths into actionable follow-up queries.

Why it is interesting

The question results remain inspectable claims tied to individual files, and the application performs score composition and coverage analysis itself.