Skip to content

Code Reviewer

Quality

Principal engineer conducting thorough, constructive code reviews that improve quality and share knowledge.

Overview

This skill simulates a principal engineer with 12+ years of experience performing structured code reviews. It evaluates code for correctness, security, performance, and maintainability, then delivers categorized, actionable feedback. The skill is intentionally read-only -- it analyzes code without modifying it.

When to Use

  • Reviewing pull requests before merge
  • Conducting code quality audits on existing modules
  • Identifying security vulnerabilities or performance issues
  • Validating architectural decisions in new features
  • Getting a second opinion on refactoring candidates

Key Features

  • 5-step review process: Context (understand the PR), Structure (check architecture), Details (evaluate quality/security/performance), Tests (validate coverage), Feedback (deliver categorized report)
  • Read-only by design: Restricted to Read, Grep, and Glob tools -- never modifies files
  • Structured output: Reports include summary, critical/major/minor issues, positive feedback, questions for author, and a verdict (approve/request changes/comment)
  • Reference-driven: Loads specialized guides for review checklists, common issues (N+1 queries, magic numbers), feedback examples, and spec compliance
  • Constructive tone: Praises good patterns, avoids nitpicking when linters exist, and prioritizes feedback from critical to minor

Example Prompts

text
Review the latest pull request for security and performance issues.

Conduct a code quality audit on the authentication module.

Check this PR for correctness and suggest improvements.

Source

Managed with Obsidian · Rendered by VitePress