review-pipelinelisted

# Review Pipeline ## Core Rule Parallelize independent auditors over a PR-scope diff. Dedupe across reports. Never widen scope beyond the diff. ## Kit Context Before starting this skill, ensure you have completed session boot: 1. Read `CODEBASE_MAP.md` for project understanding 2. Read `CLAUDE.project.md` if it exists for project-specific rules 3. Read `tasks/lessons/_index.md` for accumulated corrections (Top Rules + index) If any of these haven't been read in this session, read them now before proceeding. ## When to Use Invoke with `/review-pipeline` when: - A PR is ready and you want a multi-lens check before requesting human review - A multi-session feature has landed on a branch and you want to catch regressions - You're investigating a flaky area and want several auditors to weigh in - You suspect issues but don't know which audit applies — let the pipeline pick Not for: - Trivial single-file edits — invoke the relevant audit directly - Project-wide periodic health checks — use `/project-health-report` instead - Full architectural assessments — use `/architecture-review` or `/deepening-review` ## Scope Rules - Read-only — produces a report, never modifies code - Operates within the detected scope (recent changes by default) - Logs unrelated issues found during analysis under `tasks/todo.md > ## Not Now` - Does not duplicate findings already in CLAUDE.md or `tasks/lessons/` ## Process ### Phase 1: Resolve Scope Pick the smallest scope that captures the cha