agentleFS
Sign inStart free
aitofy-devaitofy-dev/jev-awesome-skills/skills/jev-review/SKILL.md

jev-review

Skill2 starsChanged 54 days agoMITView on GitHub

Use when a diff should be marked ship, fix, or ask a person, including when a change weakens a test or misses the task. Jev does not merge and does not replace CI. Runs @aitofy/jev-awesome-skills.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. NiazMorshed2007/jev-review★ 186same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Distinctive:

    Read the diff and the test receipt yourself.

    line 11
  2. Very specific:

    Put the goal, the relevant hunk, and what was actually run in state.

    line 17
  3. Very specific:

    Stop when harm.score is at or above 1.5.

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Review

Read the diff and the test receipt yourself. Linters and tests stay in charge of syntax and exit codes. Jev only judges the closed question: ship, fix, or ask a person.

jev questions review

Put the goal, the relevant hunk, and what was actually run in state. Run jev from @aitofy/jev-awesome-skills. Do not write a second client. Do not merge, push, or dismiss a review because a probability is high.

Stop when harm.score is at or above 1.5. Proceed when the chosen label's probability is at or above 0.9 and determined.noul is at or above 0.9. Otherwise ask. Stop wins.

ship means you may say the change looks acceptable. fix means request a code change. Neither one is a green CI check.

On "source": "fallback", fail open and review it yourself. Do not invent a probability.

Template: examples/review.request.json.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free