← ClaudeAtlas

review-and-addresslisted

Review a branch or the current diff with the project's configured reviewers run in parallel, merge their findings, and apply the warranted ones. Use for "review my changes", "review this PR/branch", "run the reviewers on the current diff with main", "review and fix the warranted feedback". Runs every reviewer in ship-it.config review.reviewers (e.g. pr-review-toolkit, vercel-react-best-practices). Also the review stage of the ship-it orchestrator. Not for watching or fixing CI (use ci-fix) or comment-only cleanup (use comment-cleanup).
pricklywiggles/fractally-claude-marketplace · ★ 1 · Code & Development · score 65
Install: claude install-skill pricklywiggles/fractally-claude-marketplace
# review-and-address: fan out reviewers, merge findings, apply warranted Review a diff with every configured reviewer in parallel, merge the findings, and (when asked or configured) apply the warranted ones. Reviewers only read; the one write step is the address. ## 1. Resolve the target and the diff - **PR, branch, or worktree given** (an argument, or passed by the ship-it orchestrator as a work-unit): review its diff, `git diff <base>...HEAD` (base defaults to `repo.mainBranch`, usually `main`). - **Nothing given** (standalone): review the current changes, the working-tree diff against `main`, or the current branch's diff with `main`. This is the "current diff with main" case. - Note the changed files; reviewers and the address step operate only on this diff. ## 2. Read config, else defaults Load the resolved config via `${CLAUDE_PLUGIN_ROOT}/scripts/load-config.sh` (defaults applied, `@FILE` refs inlined); read keys with `jq`: - `review.reviewers` (the list; if absent, default to a single `pr-review-toolkit` agent reviewer), - `review.applyWarranted` (default: true in the orchestrator; for a standalone run, report unless asked to apply), - `verify`, `houseRules`, `safety` (for the address step). ## 3. Fan out the reviewers (parallel, read-only) Run every reviewer in `review.reviewers` over the diff concurrently: spawn one subagent per reviewer in a single message so they run in parallel. Each reviews ONLY the diff and returns structured findings. Dispatch by `kind`: