code-review

name	code-review
description	Review code for bugs, regressions, maintainability risks, and missing tests.

Code Review

Use this skill when reviewing diffs, PRs, patches, or implementation plans.

Review stance:

• Findings first, ordered by severity.
• Reference exact files and lines when possible.
• Prioritize correctness, security, data loss, regressions, and missing tests.
• Avoid style comments unless they hide a real risk.
• If no serious issue is found, say so and mention residual test gaps.
• Keep summaries short and secondary to findings.