eddy
Skill120 starsChanged todayMITView on GitHub
Review the branch with Eddy, the repository's own review bot (`package-eddy/`), then answer its findings with /code-review-response. Invoke ONLY when the user asks for it by name — never on your own initiative: a review calls a paid API.
- Reads credentials
In this repository39 other files it gives its agents.
- AGENTS.mdAGENTS.md
- benchmark/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- package-gale/AGENTS.mdAGENTS.md
- package-grog/AGENTS.mdAGENTS.md
- package-jade/AGENTS.mdAGENTS.md
- package-loam/AGENTS.mdAGENTS.md
- package-re/AGENTS.mdAGENTS.md
- package-wadopoet/AGENTS.mdAGENTS.md
- wado-bundled-icu/AGENTS.mdAGENTS.md
- wado-cli/AGENTS.mdAGENTS.md
- wado-compiler/AGENTS.mdAGENTS.md
- wado-from-idl/AGENTS.mdAGENTS.md
- wado-host/AGENTS.mdAGENTS.md
- wado-lsp/AGENTS.mdAGENTS.md
- wado-manifest/AGENTS.mdAGENTS.md
- wado-run-pjrt/AGENTS.mdAGENTS.md
- wado-run-webgpu/AGENTS.mdAGENTS.md
- wado-vscode/AGENTS.mdAGENTS.md
- benchmarkSkill
- ci-timingSkill
- code-review-responseSkill
- coverage-investigationSkill
- crSkill
- debuggerSkill
- distillSkill
- git-upstream-syncSkill
- jcoSkill
- markdownSkill
- on-task-doneSkill
- optimizer-debugSkill
- profiling-wado-compilerSkill
- pull-requestSkill
- rust-renameSkill
- rustSkill
- vendor-submodulesSkill
- wado-cliSkill
- wado-performanceSkill
- wasm-optSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 13
Commit everything the review should see.
- Distinctive: line 14
Run the review in the background, its output in files:
- Very specific: line 23
Read scratchpad/eddy.json.
- Very specific: line 27
Commit the record the run wrote, package-eddy/reviews/<head>.json.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Reviewing the Branch with Eddy
Eddy reviews what the branch changes from its merge base with origin/main.
It reads the diff and a checkout of HEAD, so an uncommitted change is not
reviewed. It also writes tests into that checkout and runs them with cargo,
mise, or a tool mise installed for the project.
- Commit everything the review should see.
Run the review in the background, its output in files:
mise run eddy-review > scratchpad/eddy.json 2> scratchpad/eddy.logIt takes the lock the test tasks take, so no test runs beside it. With
no-runas the skill's argument, add--no-run: the reviewer then only reads, takes no lock, and no finding carries arepro.- Read
scratchpad/eddy.json. A failed review exits other than 0, and the line ofscratchpad/eddy.logthat starts witheddy:gives the reason. The line that starts withcost:gives what the review cost, in total and for each model; tell the user. - Commit the record the run wrote,
package-eddy/reviews/<head>.json. It holds every review of that commit, and Eddy later learns from which of its findings were addressed. - Answer the findings with the
code-review-responseskill. With no findings, say so and stop.
Reading a Finding
A finding the reviewer reproduced carries a repro: a patch against the
reviewed commit, the command in run, and expect, a text the failing run
prints. verified says whether Eddy, after the review, applied
that patch alone to a clean checkout and saw the run fail with that text.
- With
verifiedtrue, the finding is already reproduced. The log names the directory that holds the patch of finding<n>, counted from 1:git apply scratchpad/eddy/<head>/<n>.patch, and the command inrunis the failing test to fix against. Keep the test where it belongs in the tree once it passes. - With
verifiedfalse,outputsays why: the run passed, failed another way, the patch did not stand alone, or, wherepatchis empty, the test could not be tried at all. Verify the finding as any other claim. - With no
repro, no test of the reviewer's was found to reproduce it, anddetailoften says why.
One review is not repeatable: on the evaluation set
(package-eddy/eval/README.md) the same change gets different findings from
run to run. So an empty list does not clear the branch.
Requirements
CLAUDE_API_KEYin the environment.CLAUDE_MODELpicks the reviewer.gitandrgunder/usr/bin.- The main checkout, not a linked worktree: a child of
wado runcannot reach a git directory outside the current one. - Unless
--no-run: the toolchainrust-toolchain.tomlnames and the cratesCargo.locknames, already installed and fetched, and the toolsmise.tomlnames, already installed. The reviewer'scargoandmisecannot write thecargo,rustupandmisehomes.
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
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.

