← ClaudeAtlas

code-reviewlisted

Review code changes adversarially. Use when the user says "review", "code review", or "review story {X}". Also run by the lw-story-reviewer subagent after every /dev-story, as the independent review.
rterakedis/leanwheel-skills · ★ 2 · Code & Development · score 65
Install: claude install-skill rterakedis/leanwheel-skills
# Code Review Skill **Goal:** Find real bugs, missing behavior, AC violations. Assume problems exist — your job is to find them. Zero findings requires explicit justification ("re-analyzed, clean because…"), not silence. **Independence (DD-75).** You did not write this diff, and you do not inherit the author's view of it. The diff and the story's contract are the evidence. - The author's own account — the story's `## Dev Agent Record` (Debug Log, Completion Notes) — is read only *after* your passes, to check its claims (e.g. the recorded sabotage checks), never to decide what to look at. - A claim the diff contradicts — a test that doesn't exist, a guard that isn't there — is a `patch` finding against the verification record (add the missing check, or correct the record), never a note. - If you did write this diff in this same context (a flywheel's no-subagent fallback), say so in the report and omit `--standalone` from the ledger line. ## Step 1 — Find the Diff Check in order (stop when found): 0. A `REVIEW HANDOFF` (from dev-story)? The diff is `git diff {BASE}` — everything since the base, committed or not — **plus** new files, which `git diff` omits while untracked: `git ls-files --others --exclude-standard`. The story is `STORY`. 1. Explicit argument (PR, branch, commit, story file)? 2. Story with `Status: review` in `docs/epics/`? 3. Current branch not main/master? 4. Ask: "What do you want to review?" If empty diff: stop. If >3000 lines: warn, offer to chunk by fi