review

Review code changes with a checklist covering correctness, security, performance, and quality.

Updated Dec 22, 2025
One-click install
npx skills add https://github.com/royhenengel/Claude-Customizations --skill review-royhenengel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review
Source: https://github.com/royhenengel/Claude-Customizations/tree/main/skills/Code-Quality/review
Command: npx skills add https://github.com/royhenengel/Claude-Customizations --skill review-royhenengel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of reviewing code changes, ensuring comprehensive checks for correctness, security, performance, and quality.

Core Features & Use Cases

  • Systematic Code Analysis: Applies a detailed checklist to identify potential issues.
  • Contextual Review: Adapts to different review targets like PRs, branches, or staged changes.
  • Use Case: Before merging a pull request, use this Skill to perform a thorough review, catching bugs, security flaws, and style inconsistencies early in the development cycle.

Quick Start

Use the review skill to analyze the staged code changes.

Frequently Asked Questions about review

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

FAQPage Schema
How do I automate code review for a pull request?

To automate code review for a pull request, this Skill applies a comprehensive checklist covering correctness, security, performance, and code quality to generate structured output with severity ratings and actionable suggestions.

What does a systematic code review checklist cover?

A systematic code review checklist covers correctness, security, performance, code quality, testing, documentation, and architecture to ensure comprehensive evaluation of code changes before merging.

Can I review specific commit ranges or staged file paths?

Yes, you can review specific commit ranges or file paths, as the Skill supports various review targets including PRs, branches, commit ranges, and staged changes to adapt to your workflow.

What is the best way to catch security flaws and bugs before merging?

The best way to catch security flaws and bugs before merging is to perform a contextual review on your branch or PR, which identifies potential issues and outputs actionable suggestions with severity ratings.

Does the code review output include severity ratings for issues?

Yes, the code review output includes severity ratings for identified issues, generating a structured review with actionable suggestions to help prioritize debugging and quality assurance efforts.

Why should I use an automated assistant for quality assurance instead of manual checks?

You should use an automated assistant for quality assurance to systematically catch bugs, security flaws, and style inconsistencies early in the development cycle, ensuring comprehensive checks that manual reviews might miss.