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.

Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
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.
Add only project context that changes the result: change scope, business goal, stack, upstream/downstream deps, known risks, team norms.
Treat role reports as optional, source-identified context; use Product and UI/UX reports only when this change touches their concerns.
Default to Markdown; switch formats only when the user asks.