code-review

Automate code review with severity-based analysis, prioritization, and bug fix verification.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill facilitates efficient code review processes by providing structured guidance, prioritizing issues, and verifying bug fixes, thereby improving code quality and review accuracy.

Core Features & Use Cases

  • Targeted Review Guidance: Guides reviewers through selecting and inspecting the appropriate code change targets like PRs, branches, or local modifications.
  • Prioritized Findings: Highlights issues based on severity levels such as bugs, regressions, or security risks, supported by evidence from code.
  • Bug Fix Verification: Assists in independently reproducing and confirming bug fixes through structured steps, ensuring the correctness of fixes before approval.
  • Use Case: When a developer submits a pull request, this Skill enables the reviewer to systematically analyze the changes, identify critical issues, and verify fixes with minimal manual effort.

Quick Start

Review a pull request or branch, then analyze the code for bugs, regressions, or security issues, and verify bug fixes independently to ensure correctness.

Frequently Asked Questions about code-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?

Automated code review analyzes pull requests by providing structured, severity-based analysis and prioritized findings to identify bugs, regressions, and security risks. It guides reviewers through inspecting code changes and verifying bug fixes using evidence from the codebase.

What is the best way to prioritize issues found during code review?

Prioritizing code review issues is handled by evaluating severity levels such as bugs, regressions, or security risks. The process highlights critical findings supported by evidence from the code, reducing manual review time and improving code quality evaluation accuracy.

How do I verify a bug fix before approving a pull request?

Bug fix verification involves independently reproducing and confirming the fix through structured steps. This ensures the correctness of the fix before approval, systematically evaluating code quality and reducing review errors during the pull request process.

Can I review local code modifications or do I need a pull request?

Code review can target various code change targets including pull requests, branches, or local modifications. This flexibility allows developers to systematically analyze changes, identify critical issues, and verify fixes regardless of the specific codebase format used.

Does automated code review work with different codebases?

Automated code review works across various codebases to provide systematic, evidence-based code quality evaluation. It meets the need for structured analysis by guiding reviewers through selecting and inspecting appropriate code change targets like branches or pull requests.

Why should I use structured code review instead of manual inspection?

Structured code review reduces review time and errors by providing severity-based analysis, prioritization, and bug fix verification. Manual inspection lacks this systematic, evidence-based evaluation, increasing the risk of missing critical bugs, regressions, or security risks.