code-review

Name: code-review
Availability: InStock
Author: sun2443

Review code changes for security, performance, and correctness issues.

Updated Apr 8, 2026

Search Tags:#diff analysis #code review #performance #pull request #error handling #security audit #correctness

Ready to run

npx skills add https://github.com/sun2443/designer-skills --skill code-review-sun2443

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/sun2443/designer-skills/tree/main/engineering/skills/code-review
Command: npx skills add https://github.com/sun2443/designer-skills --skill code-review-sun2443

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you catch defects and risks in pull requests before they reach production, reducing security exposure, performance regressions, and correctness bugs.

Core Features & Use Cases

Security review: flags common vulnerabilities and insecure patterns (e.g., injection, authz/authn issues, secrets exposure).
Performance review: identifies likely bottlenecks such as N+1 queries, complexity issues, unbounded loops, and resource leaks.
Correctness & maintainability review: checks edge cases, error handling, race conditions, and improves readability and test/documentation coverage.
Use Case: review a PR that changes request validation and database queries to ensure you didn’t introduce injection risks, missing edge cases, or inefficient query patterns.

Quick Start

Run the skill with the command: /code-review <PR URL or file path>.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review a pull request for security vulnerabilities and performance issues?▼

To review a pull request for security vulnerabilities and performance issues, analyze the code diff to identify injection risks, authz flaws, N+1 queries, and resource leaks before merging. This process produces a structured review with critical issues, file-line suggestions, and an approve or request-changes verdict.

What is automated code review for pre-merge gating?▼

Automated code review for pre-merge gating is the process of evaluating patch outputs and file-path change sets to catch correctness defects, maintainability issues, and security exposure before code reaches production. It generates a structured summary with actionable suggestions and a clear merge verdict.

How do I check code changes for edge cases and error handling defects?▼

To check code changes for edge cases and error handling defects, perform a correctness and maintainability review on the pull request diff. This identifies missing edge case coverage, race conditions, and readability problems, yielding a structured report with specific file and line suggestions.

Can I use diff analysis to find maintainability and correctness bugs in patch outputs?▼

Yes, you can use diff analysis to find maintainability and correctness bugs in patch outputs. By evaluating the code changes, you can detect insecure patterns, unbounded loops, and error handling gaps, resulting in a structured review summary with a clear verdict to approve or request changes.

Does code review work with specific file paths or do I need a full pull request URL?▼

Code review works with both specific file paths and full pull request URLs. You can run the analysis on file-path change sets or patch outputs directly, generating a structured summary with critical issues, file and line suggestions, and a final approve or request-changes verdict.

What is the best way to audit code for injection risks and missing authorization?▼

The best way to audit code for injection risks and missing authorization is to perform a security review on the pull request diff. This flags common vulnerabilities and secrets exposure, producing a structured review with critical issues, targeted file-line suggestions, and a clear verdict.