Second Opinion

Second Opinion is a contributor-driven repository for building a structured code review skill. The system uses a prompt pipeline (tagger → compiler → reviewer) and a controlled taxonomy to produce attributable review outputs.

This repo includes sample foo assets in each contributor asset directory to show formatting and organization; exclude them from real reviews.

Install

Codex CLI

From the Codex CLI prompt, run:

$skill-installer https://github.com/PingCAP-QE/second-opinion

Restart Codex after installation to load the skill.

Claude Code

Clone the repository into your Claude skills directory:

# Global install (available in all projects)
git clone https://github.com/PingCAP-QE/second-opinion ~/.claude/skills/second-opinion

# Or project-local install
git clone https://github.com/PingCAP-QE/second-opinion .claude/skills/second-opinion

No restart required. The skill is immediately available as /second-opinion or triggered automatically when you ask for a code review second opinion.

To update later:

git -C ~/.claude/skills/second-opinion pull

Usage

Use second-opinion to review a diff, PR, or commit range.

Minimum prompts:

Give second opinion on this change.

请给这个改动 second opinion。

Verbose prompt (extra requirements):

Give second opinion on this change. Use English output, prioritize pkg/expression and tests, focus on correctness plus MySQL date/time semantics and nullability, and include verification commands for high/critical findings.

Workflow contract (applies even with the minimum prompt):

• Infer review-output language from the prompt that triggers second opinion, and use that language directly without asking a separate question.
• Run tagger → compiler → reviewer.
• Write second_opinion_meta.json, second_opinion.md, and second_opinion.json in the repository root.
• If GitHub posting is requested or confirmed, write second_opinion_github_comments.json in the repository root.
• Chat output is supplementary and does not replace file outputs.

GitHub comment posting contract:

• GitHub side effects require explicit user intent.
• If the initial request did not ask for posting, ask after review outputs are complete.
• GitHub comments must be in English.
• Prefer comment modes in order: inline, then file, then general.
• File comments must use PR review comment semantics (subject_type=file).
• If inline posting fails due to unresolved line context, retry as file comment before general comment.
• Each GitHub comment must end with Source: / | [Second Opinion](https://github.com/PingCAP-QE/second-opinion) on one line.
• Do not duplicate one finding across multiple comment modes.
• Do not add an extra review body comment per finding when inline/file comments already exist.
• Do not add repository shell posting scripts.
• For actual posting, use gh CLI; if gh is unavailable or unauthenticated, fail posting explicitly.