← ClaudeAtlas

jevaluate-reportlisted

Turns a Jevaluate rating a team agrees with into one Markdown report its coding agents can work from before a pull request: the verdict, a ranked fix table and one section per fix with the line it rests on, the TypeSafe docs behind it, a change to try and a test to run on the team's own eval. Use after rating a project with jevaluate-private (or jevaluate-publish) and agreeing with the result, when a team wants a file its agents can work through, or on "/jevaluate-report" with a repo, rating or folder.
tiffygk/jev-mode · ★ 15 · Data & Documents · score 70
Install: claude install-skill tiffygk/jev-mode
# Jevaluate Report The workflow this skill fits: build with Jev Sources open, rate the work with `jevaluate-private`, and once you agree with the rating, run this skill. It writes one Markdown file that you point your coding agents at to work through the fixes before you open a pull request. The rating is a pair-programming check, not a score to publish, and this skill never posts anything. `<skill>` below is this skill's folder. ## Contents - The framing rule - Intake - Steps - After the fixes - In Codex - Files - Enforced by ## The framing rule Jevaluate checks a design against TypeSafe's documented practice. That practice isn't shown to matter for this product until the team tests it on their own eval, and the people who built the project know it far better; what looks like a departure may be how they made something work. So every fix is advice to test: a change to try, and a test with a bar set before the run. The report says so in plain words in its opening, for the person and for their agent. Every fix section has five labels (`scripts/report_check.py` checks them), in this order: **What we saw.**, **Why it matters.**, **Source.**, **Suggested change.**, **How to check it.** In them: - **Suggested change** starts with "Try" or "Consider". - No promise, outside quotes, in Suggested change, Why it matters, the opening, the Rating section or the title: "this fixes", "will fix", "will reduce", "solves", "must", "rates 4" and the like. `scripts/report_check.py` holds