← ClaudeAtlas

code-reviewlisted

Run a multi-LLM code review on a pull request — gather the diff, dispatch reviewer CLIs in parallel via the file-write contract, synthesize a Korean summary, and post inline comments tagged by severity and model signature. Use this for any PR review whether the PR was just opened by flow:deploy or already exists on GitHub. Even when the user says "review PR
gitgitWi/council-flow · ★ 1 · Code & Development · score 55
Install: claude install-skill gitgitWi/council-flow
# flow:code-review — Multi-LLM PR review Code-review is the review-only half of the deploy pipeline, extracted so it can run on **any** PR — not just one this session created. `flow:deploy` invokes this skill automatically after opening the PR. You can also invoke it directly on any existing PR. ## Inputs 1. **PR number** — required, but auto-detected from the current branch if omitted (`gh pr view --json number --jq .number`). If the current branch has no PR, ask the user for the number. 2. **Plan context path** — optional. If invoked inside a flow task worktree, point at `.planning/<date>-<task>/plan.md`. If not available, omit; reviewers work from the diff alone. 3. **Output directory** — auto-resolved (see "Output directory resolution" below). Override only if the user asks. ## Preconditions - `gh` CLI authenticated against the PR's repo (`gh auth status`). - PR exists and is open. Closed/merged PRs can be reviewed but warn the user. - `git` available; the diff is computed against the PR's base branch (`gh pr view <PR> --json baseRefName`). - Reviewer CLIs (`gemini`, `opencode`) — pre-flight per `../../references/multi-llm.md`. Missing CLIs are skipped, not fatal. If `gh` is unauthenticated or the PR does not exist, stop and tell the user. Do not "fix it up" silently. ## Output directory resolution Resolve in this order; first match wins: 1. **Flow task worktree** — if the current working directory is inside a worktree whose branch matches the PR's `headRefName`