Code PR Review Skill

Produce thorough, actionable PR reviews laser-focused on four pillars: syntax quality, no repeated code (DRY), performance, and security. Reviews should feel like they came from a senior engineer who is helpful, direct, and specific — not a linter or a checklist robot.

Input Formats

Accept any of these:

• Raw git diff (pasted inline or in a file)
• GitHub / GitLab PR URL — fetch the diff via web_fetch if available
• Uploaded files — read changed files directly
• Inline code snippets described as "changes" or "before/after"
• Partial context — review what's available; flag if more context would change the verdict

Review Structure