wado-lang/wado / .claude/skills/eddy
eddy
VerifiedReview 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.
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. -
Push the record the run wrote, a file under
reviews/<head>/in the wiki's clonescratchpad/wiki. That directory holds every review of the commit, and Eddy later learns from which of its findings were addressed. A rejected push takesgit -C scratchpad/wiki pull --rebasefirst: every review adds its own file, so nothing conflicts.git -C scratchpad/wiki add reviews git -C scratchpad/wiki commit -qm "Record Eddy's review of $(git rev-parse HEAD)" git -C scratchpad/wiki push -qIn a Claude Code cloud session the git proxy serves no wiki, so the push carries a token itself. The maintainer's cloud environment sets
GITHUB_TOKENto a personal access token for this; another environment has none unless its owner provides one:git -C scratchpad/wiki -c http.extraheader="Authorization: Basic $(printf 'x-access-token:%s' "$GITHUB_TOKEN" | base64 -w0)" push -q. -
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 321k | Updated | Claude CodeCodex | Verified | Install |