← ClaudeAtlas

repo-reviewlisted

Whole-repository review/audit of an existing or inherited codebase. Use when the user says "review this repository", "audit this codebase", "do a full code review of the repo", "what's wrong with this app", "I just inherited this project", or asks for a multi-axis sweep (e.g. "review for 1. performance 2. code smells 3. structure"). NOT for reviewing a single diff/PR (use the /code-review command) or a one-file change.
mickzijdel/dev-hooks · ★ 0 · Code & Development · score 71
Install: claude install-skill mickzijdel/dev-hooks
# repo-review A top-level, **whole-repository** health-check for an existing or inherited codebase. This is the entry point for *reviewing a repo as a whole* — the stack-agnostic counterpart to [[rails-audit]] (which does the same for Rails apps). It is deliberately distinct from the `/code-review` command: `/code-review` reviews the **current diff**; this skill reviews the **whole repo** across many axes and ends in a written, severity-ranked report. **The design principle is delegate, don't re-derive.** Wherever a specialist skill or command already owns an axis, run only the cheap detection here and hand the deep work to it. The new value this skill adds is (a) the whole-repo scoping, (b) the orchestration across axes, and (c) the axes nobody else covers (performance, architecture, secrets-scan, suite *runnability*, genericization). **Report-only.** This skill diagnoses; it does not change code. Surfacing findings the user can triage is the goal — auto-fixing across a whole unfamiliar repo is too high blast-radius. If the user wants fixes after reading the report, that's a separate, scoped follow-up (e.g. run `/simplify` on a specific area, or the relevant fix skill). ## How to run 1. **Confirm the repo root** and get the lay of the land. Run the preflight to see which stacks and surfaces are present and which delegated skills apply: ```bash bash "$CLAUDE_PLUGIN_ROOT/skills/repo-review/scripts/detect_stack.sh" . ``` It reports the language(s), whether t