jevbooks

← All projects

prose-check

vgeshel/prose-check

Checks a coding agent's final reply against project writing rules.

Verification & Guardrails0.99Runner-up: Evaluation & Benchmarking
Automated README summary

Automatically summarized from the README on 18 Oct 2026; not a run by jevbooks. Run instructions and author-reported outcomes still need verification.

What it is

A plugin for Claude Code, Codex, and Muse Code that checks each turn's final reply against the writing rules in the project's CLAUDE.md or AGENTS.md, and asks the agent to rewrite a reply that breaks a rule.

How it uses Jev

Jev judges whether the agent's final reply breaks the writing rules extracted from the instruction file. The plugin sends one request per checked reply; when Jev reports a broken rule, the plugin asks the agent to rewrite the reply once.

Technique worth stealing

Extract the project's writing rules from its instruction file, then have Jev judge each final reply against them and trigger one rewrite.

Try it

claude plugin marketplace add vgeshel/prose-check; claude plugin install prose-check@prose-check; then run /prose-check doctor

View on GitHub

Start using Jev: API key and your first request →

Model judgments from README excerpts

Project signals use repository metadata, an existing summary and the first 700 README characters, not the full project. “Not found” means not detected in that material; it does not establish absence. These are the original judgments with recorded models and dates, not source audits or run results.

Models & evaluation dates

Inclusion gate
jev-1.13.0
Project signals
jev-1.13.0
Category
jev-1.13.0
Pattern tags
jev-1.13.0

Evidence

These signals use repository metadata, an existing summary and at most 700 cleaned README characters. ≥ 0.60 means reported in that excerpt; ≤ 0.40 means not found there. The middle band is inconclusive. None is a source-code audit or a test result. The runnable-tool question excludes research experiments; the recommendation question asks for a learning shortlist, not a quality verdict.

  • Jev is core to the projectFound in material0.73
  • Shows a System One patternnot found in the excerpt0.17
  • Describes handling uncertaintynot found in the excerpt0.05
  • Reports measured numbersnot found in the excerpt0.06
  • Is a runnable toolFound in material0.94
  • Top-10 learning shortlist signalnot found in the excerpt0.24
  • Is a replica of the modelnot found in the excerpt0.04
  • Solves a common problem (0–2)score on a 0–2 scale1.22 / 2
  • About JevFound in material0.97
Signals
Jev is core to the project0.73Shows a System One pattern0.17Describes handling uncertainty0.05Reports measured numbers0.06Is a runnable tool0.94Top-10 learning shortlist signal0.24Is a replica of the model0.0400.51Solves a common problem (0–2)1.22 / 2012

no-judgment band (0.40–0.60)

Design patterns
Viewfinder0.50Fail open, fail closed0.4600.51

no-judgment band (0.40–0.60)

The Jev model and date for each judgment stage are listed above. Card written by DeepSeek V4.1 Flash from the README on 18 Oct 2026.