code-review

Review pull requests with a security-first, three-pass checklist and severity labels.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/droxey/skills --skill code-review-droxey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/droxey/skills/tree/main/code-review
Command: npx skills add https://github.com/droxey/skills --skill code-review-droxey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code review quality varies between reviewers and teams, leading to missed security issues, performance regressions, and brittle or untested changes.

Core Features & Use Cases

  • Systematic multi-dimension checklist: Reviews security, performance, correctness, maintainability, testing, accessibility, and documentation in a structured order to reduce random scanning.
  • Security-first hardening guidance: Covers common high-impact risks such as SQL injection, XSS, CSRF, auth/authz issues, secrets handling, and safe file upload practices.
  • Defined review process and severity labeling: Uses a three-pass approach (high-level structure, line-by-line detail, edge-case hardening) plus Critical/Major/Minor/Nitpick severity to make decisions consistent.
  • Actionable feedback patterns: Emphasizes specificity, explaining risk, suggesting concrete fixes, and separating blocking from non-blocking feedback.

Quick Start

Use this skill to review a pull request by running through the First Pass, Second Pass, and Third Pass checklists and tagging each comment with an appropriate severity level.

Frequently Asked Questions about code-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform a consistent pull request code review?

Perform a pull request code review using a three-pass process: high-level structure, line-by-line detail, and edge-case hardening. Tag feedback with Critical, Major, Minor, or Nitpick severity levels to ensure consistent review outcomes across security, performance, and maintainability.

What is the best way to check security vulnerabilities during a PR review?

Check security vulnerabilities during a PR review by applying a security-first checklist covering SQL injection, XSS, CSRF, auth/authz issues, secrets handling, and safe file upload practices. This systematic approach reduces random scanning and catches high-impact risks early.

How do I structure code review feedback to be actionable?

Structure code review feedback by being specific, explaining the risk, suggesting concrete fixes, and separating blocking from non-blocking comments. This actionable feedback pattern ensures developers understand the severity and required changes without ambiguity.

What dimensions should a code review checklist cover?

A code review checklist should cover security, performance, correctness, maintainability, testing, accessibility, and documentation. Reviewing these dimensions in a structured order reduces random scanning and standardizes pull request quality across teams.

Why does code review quality vary between team members?

Code review quality varies between team members due to inconsistent processes and lack of severity labeling. Establishing team review standards with a defined three-pass approach and explicit anti-pattern guidance prevents missed security issues and performance regressions.