branch-reviewlisted

# Branch Review (Multi-Agent) ## DIFF DISCIPLINE (top-level rule) **The diff is the only anchor.** This review does NOT inspect the whole project — it inspects the changes between `<base>` and `HEAD`. If this skill triggers without a diff: abort and point to `full-project-review`. Allowed reads: 1. All files touched by the diff — completely (context around the change). 2. Direct imports/callers/call sites of changed symbols — targeted, not broad. 3. Config/manifest files for tech-stack detection. 4. System-wide locations ONLY when a diff change demonstrably affects them (e.g. new auth middleware → check other routes). Mark in the finding: `Diff trigger: <file:line>`. Forbidden: - Repo-wide scans without diff context ("let me check all controllers"). - Findings about unchanged legacy code not touched by the diff. - Existing tech-debt lists with no connection to the current diff. ### Anti-Rationalization Table These thoughts mean STOP — you are rationalizing scope drift. Each maps to the rule that overrides it. | Rationalization | Reality | | --- | --- | | "While I'm here, let me also check the rest of this file." | Only diff-touched lines + their direct context. Untouched code in the same file is out of scope. | | "This whole module is poorly designed, I'll note it." | No finding without a `Diff trigger: <file:line>`. Untouched tech debt belongs in `full-project-review`. | | "The diff is tiny, so I'll broaden to add value." | A small diff yields a small report. Paddin