code-review

name	code-review
description	Use this skill when you need a risk-driven code review of a PR/diff with severity-ranked findings and actionable fixes; triggers include code review, PR review, and 代码审查.

Code Review

中文版： See the corresponding Chinese skill.

When to Use

• Need to review a PR / diff / commit and catch logic, security, financial-loss, or maintainability risks before merge.
• Need a P0/P1/P2-ranked report with locations and actionable fix guidance.
• Need a QA / engineering-quality lens beyond author self-review.

Workflow

1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
2. Before reviewing, confirm both an identifiable code version and its reviewable changes; if either is missing, return a blocked result and request the exact material.
3. Add only project context that changes the result: change scope, business goal, stack, upstream/downstream deps, known risks, team norms.
4. Treat role reports as optional, source-identified context; use Product and UI/UX reports only when this change touches their concerns.
5. Default to Markdown; switch formats only when the user asks.

Core Constraints

• Risk-driven: prioritize production failures, financial loss, security, and core maintainability — not naming/indent noise.
• Evidence-based: prefer file path, line, or snippet plus trigger path and impact for each finding.
• Two gates: require both identifiable code version (for example repository + PR / commit / branch / tag / revision) and reviewable change (for example diff/patch, changed-file contents, or an accessible base-to-head range). Code identity, change content, and role reports cannot substitute for one another.
• If either gate is missing, explicitly return status: blocked and distinguish missing_code_identity from missing_reviewable_change; do not claim review completion, recommend merge, or invent code findings.