second-opinion
Use when the user asks for a second-opinion review from another agent (e.g., "get a second opinion", "review with pi", "review using gpt-6-astra", "/second-opinion"), or when review-code runs with `-2o`. Runs a fresh pi session (or Claude Code, when already inside pi) on the review-code skill and relays its review.
How do I install this agent skill?
npx skills add https://github.com/lwlee2608/agent-skills --skill second-opinionIs this agent skill safe to install?
No partner audit is available yet. Read the source before installing.
What does this agent skill do?
Second Opinion
Get a code review from a different agent by running a fresh headless session of it. The user wants that agent's take, not yours — relay it, don't redo it.
When review-code -2o runs this skill, these rules govern only the relayed review. The caller's own review still runs, and a failure here does not stop it.
Pick the reviewer
If PI_CODING_AGENT is true, you are running in pi — the reviewer is Claude Code (claude). Otherwise the reviewer is pi.
Assume the reviewer is installed, its default model is configured, and the review-code skill is available to it. Don't probe for any of these — if it fails, surface the error and stop.
Rules
-
Resolve the target in
review-code's vocabulary. Don't compute the diff yourself.- PR number →
pr <N> - "PR" with no number →
pr <N>for the current branch's PR - Ref range (e.g.,
main...HEAD),all,codebase, or a path → verbatim - Otherwise →
diff
- PR number →
-
Pass the user's model verbatim to
--model, or omit--modelif they named none — the reviewer falls back to its configured default. -
Run the reviewer's command from the repo root, substituting target and model. The prompt is the same for both:
Use the review-code skill to review <target> --no-sub in this repo. Do not modify any files.pi:
pi -p \ --model <provider/model> \ --exclude-tools edit,write \ --name "review: <target>" \ "<prompt>"Claude Code:
claude -p \ --model <model> \ --disallowedTools Edit Write NotebookEdit \ --allowedTools "Bash(git *)" "Bash(gh *)" \ --no-session-persistence \ "<prompt>"-pprints only the final answer, so the output is safe to read in the main session.- The tool flags keep the reviewer from "fixing" findings while leaving
gitandghusable. - Reviews can take several minutes — use the longest allowed timeout or run it in the background.
-
Never resume a session. No
-c,-r,--resume,--session,--session-id, or--fork— prior context pollutes the review. -
Never inline the diff in the prompt, and never pass
-2oto the reviewer.review-coderesolves the target itself, a large diff breaks shell quoting, and the flag would make the reviewer spawn you back. -
Relay the review verbatim. Don't summarize, re-rate, or add your own findings.
-
On non-zero exit, print the error and stop. Never fall back to a review of your own.
Verification procedure
- Every reported finding has a
path:linecitation. If findings lack them, the reviewer likely never loadedreview-code— re-run once, then report. A clean review with no findings needs no citations. - If pi rejects the model, check
pi --list-models <name>and retry with a listed name.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/lwlee2608/agent-skills/second-opinion">View second-opinion on skillZs</a>