code-reviewer

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

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill code-reviewer-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill code-reviewer-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviewers help you identify defects and risks before they ship by turning an unlabeled change into a structured, prioritized assessment of correctness, security, performance, and readability.

Core Features & Use Cases

  • Severity-based findings: Produces Critical (Must Fix), Warning (Should Fix), and Suggestion (Nice to Have) items with concrete fixes.
  • Multi-dimension scanning: Covers security vulnerabilities, correctness bugs, performance issues, readability/maintainability, DRY violations, error-handling gaps, and missing tests.
  • Actionable workflow for PRs/MRs: Works on snippets, file paths, diffs, or PR/MR references and ends with a clear verdict (Approve / Request Changes / Comment).

Quick Start

Ask the skill to review your pull request diff and report Critical security issues first, then correctness, performance, and readability problems.

Frequently Asked Questions about code-reviewer

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 bugs?

To review a pull request for security vulnerabilities and bugs, submit your diff, file paths, or snippets for analysis. The review prioritizes security and correctness findings, outputting categorized severity levels with concrete fixes and a final merge verdict.

What is the best way to find code smells and performance issues in a diff?

The best way to find code smells and performance issues in a diff is to run a multi-dimension scan on the changes. This surfaces readability problems, DRY violations, and performance bottlenecks, categorizing them into Critical, Warning, and Suggestion items.

Can I use this code review process on individual file paths instead of full PRs?

Yes, you can use this code review process on individual file paths, snippets, diffs, or full PR/MR references. It audits code quality and potential regressions regardless of the input size, ending with a clear Approve, Request Changes, or Comment verdict.

How does severity-based code review prioritize fixes before merging?

Severity-based code review prioritizes fixes by categorizing findings into Critical (Must Fix), Warning (Should Fix), and Suggestion (Nice to Have) items. It evaluates security first, then correctness, performance, and readability to generate actionable fixes.

Does automated code review check for missing tests and error-handling gaps?

Yes, automated code review checks for missing tests and error-handling gaps as part of its multi-dimension scanning. It identifies these maintainability problems alongside security vulnerabilities and correctness bugs before providing a final merge verdict.

What are the limitations of using AI code review for regression detection?

AI code review limitations include relying solely on provided snippets, file paths, or diffs for regression detection. It cannot execute code or access runtime environments, meaning it audits static code quality and potential risks rather than validating actual runtime behavior.