code-review

Reviews code for bugs, security vulnerabilities, readability, and performance issues.

1|Updated Sep 3, 2026
One-click install
npx skills add https://github.com/amanpal3/SKILLs --skill code-review-amanpal3
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/amanpal3/SKILLs/tree/main/.agent/plugins/coderabbit/skills/code-review
Command: npx skills add https://github.com/amanpal3/SKILLs --skill code-review-amanpal3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews are time-consuming and inconsistent, often missing security vulnerabilities, performance bottlenecks, and maintainability issues that surface later as production bugs. ## Core Features & Use Cases - Structured Quality Audits: Applies checklists covering readability, naming conventions, error handling, and clean code patterns like early returns and DRY enforcement. - Security & Performance Detection: Identifies SQL injection, XSS, hardcoded secrets, N+1 queries, and algorithmic inefficiencies with concrete before/after fixes. - Use Case: Before merging a pull request, ask for a review of the changed files and receive a structured report listing issues by severity, suggested improvements, and refactored code snippets. ## Quick Start Review this code file for bugs, security risks, and readability issues and suggest refactored improvements.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I review code for security vulnerabilities?▼

Check all user input paths for validation, verify queries use parameterized statements instead of string concatenation, confirm secrets come from environment variables, and ensure authentication and authorization checks protect every resource. The review covers SQL injection, XSS, CSRF, IDOR, and path traversal.

What should a code review checklist include?▼

A thorough checklist covers readability, naming conventions, function size, error handling, security checks, and performance patterns. Prioritize correctness first, then security, readability, and performance in that order.

How to detect performance problems during code review?▼

Look for O(n) array lookups that could use Maps, sequential awaits that should use Promise.all, N+1 database queries, unbounded queries without pagination, and synchronous file operations blocking the event loop.

When should I refactor code instead of just fixing bugs?▼

Refactor when functions exceed 30 lines, files exceed 300 lines, logic is duplicated, or nesting goes beyond 3 levels. Cover existing behavior with tests first, make one small change at a time, and run tests after each change.

What are common code review red flags?▼

Instant red flags include empty catch blocks that swallow errors, console.log left in production code, hardcoded credentials or localhost URLs, SELECT * queries, eval() with user data, and Math.random() used for security tokens.