code-review

Reviews pull requests and code changes for correctness, security, performance, and maintainability.

3|Updated Aug 26, 2026
One-click install
npx skills add https://github.com/Fabric-Pro/fabric-oss --skill code-review-fabric-pro
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/Fabric-Pro/fabric-oss/tree/main/.cursor/skills/code-review
Command: npx skills add https://github.com/Fabric-Pro/fabric-oss --skill code-review-fabric-pro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Code reviews are often inconsistent, superficial, or miss critical issues like security vulnerabilities and logic errors. This Skill provides a systematic review framework with checklists, severity levels, and structured feedback templates so every pull request gets thorough, actionable scrutiny. ## Core Features & Use Cases - Structured Review Checklists: Covers correctness, security, performance, maintainability, testing, and code style with concrete verification questions. - Severity-Based Feedback: Classifies findings as CRITICAL, MAJOR, MINOR, SUGGESTION, or PRAISE so teams know what blocks a merge versus what is optional. - Anti-Pattern Detection: Flags common problems like silent failures, callback hell, god functions, SQL injection, and hardcoded secrets with before/after code examples. - Use Case: Before merging a teammate's authentication PR, run a review that catches a missing auth check on the password-change endpoint and unhashed password storage, then deliver formatted feedback with severity labels. ## Quick Start Review this pull request and provide feedback organized by severity level with specific line references and suggested fixes.

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 systematically?▼

Start with a high-level pass reading the PR description and file list, then deep-review critical paths like security and data integrity first. Classify each finding by severity (critical, major, minor, suggestion) and give line-specific, actionable feedback with code examples.

What should I check during a code security review?▼

Verify input validation on all user data, protection against SQL injection, XSS, and CSRF, and that secrets live in environment variables rather than source code. Also confirm authentication and authorization checks exist on sensitive endpoints and rate limiting on public ones.

When should a code review block a merge?▼

Block merges for security vulnerabilities, data loss risks, broken functionality, missing critical tests, and major performance issues. Style improvements, refactoring suggestions, and minor optimizations should be approved with comments instead.

How do I give constructive code review feedback?▼

Point to exact lines with concrete before-and-after code suggestions, explain why each change matters, and balance criticism with praise for well-done patterns. Use a consistent format like [SEVERITY] Issue - Suggestion so authors can prioritize fixes.

What are common code review anti-patterns to flag?▼

Watch for silent failures where catch blocks swallow errors, deeply nested callbacks instead of async/await, and god functions handling validation, processing, and persistence in one block. Also flag magic numbers, hardcoded credentials, and missing test coverage for edge cases.