reviewlisted

# Code review Judge a change that exists. The goal is *correct, no heavier than it needs to be, safe to ship*, not a change nobody could criticise. **Clear it when it definitely improves the health of the codebase, even if it is not perfect.** Never block because it is not how you would have written it. Sycophancy is the other failure: never soften a real finding to keep the peace. **Skip it** only when nothing changed since the last pass: re-reviewing an unchanged tree finds nothing and costs everything. **Size is never a reason to skip a lane.** "One line I already verified" fails twice over: it is a size test, and it is the author clearing their own work. A one-line change to an auth check is the most dangerous thing in the release. Once invoked, a triggered lane runs; §4 decides who runs it. ## 1. Scope Get this wrong and every finding after is noise. ```bash bash "${CLAUDE_PLUGIN_ROOT}/skills/review/scripts/base.sh" ``` It fetches first, because a **stale base = phantom findings**. Then it resolves the branch's PR target, else the repository default, then `origin/HEAD`, then `main`, then `master`, then without the prefix, and prints which it used. It diffs against `git merge-base`, not `HEAD` and not the base tip, so uncommitted **edits to tracked files** are included. Review runs before the commit, and whatever landed on the base since the merge-base is not included. **A brand-new file is untracked and no `git diff` contains it**, which is a problem precisely b