review-code

Review completed code diffs for correctness, security, performance, and architecture risks.

3|1|Updated May 10, 2026
One-click install
npx skills add https://github.com/nuttaruj/rolepod --skill review-code-nuttaruj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-code
Source: https://github.com/nuttaruj/rolepod/tree/main/core/skills/review-code
Command: npx skills add https://github.com/nuttaruj/rolepod --skill review-code-nuttaruj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams perform disciplined, risk-aware code reviews before merge or release, so bugs, security gaps, weak tests, performance regressions, and architectural mistakes are caught before they land.

Core Features & Use Cases

  • Risk-based reviewer selection: Routes review work to the right specialist for security, correctness, performance, UI, or architecture concerns.
  • Adversarial review for high-risk changes: Escalates sensitive diffs such as auth, billing, migrations, secrets, crypto, tokens, and payments to a stricter fresh-context review path.
  • Structured findings and fix loop: Produces severity-ordered findings with file and line references, fix direction, and a clear recommendation for approval or rejection.
  • Use cases: Ideal for pre-merge reviews, validating delegated agent work, auditing public API or schema changes, and pressure-testing complex multi-file diffs before shipping.

Quick Start

Ask the AI to review your completed diff for correctness, security, performance, architecture, UI, and test quality, then return a severity-ordered review report with merge guidance.

Frequently Asked Questions about review-code

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

FAQPage Schema
How do I review a complex multi-file diff for merge readiness?

To review a complex multi-file diff for merge readiness, route the completed code changes through a risk-based reviewer selection that identifies correctness, security, performance, UI, architecture, and testing risks. This produces severity-ordered findings with file and line references, plus clear merge approval guidance.

What is adversarial code review for high-risk surfaces like auth or billing?

Adversarial code review for high-risk surfaces like auth or billing applies a stricter fresh-context review path to sensitive diffs involving secrets, crypto, tokens, or payments. This process pressure-tests the changes to catch security gaps and correctness bugs before they land in the main branch.

How do I audit public API or schema changes before shipping?

To audit public API or schema changes before shipping, you review the completed diff for architectural and correctness risks using a structured validation process. This generates a canonical review report containing severity-ordered findings with file and line references, along with approval or rejection guidance.

Does a structured code review check for performance regressions and weak tests?

Yes, a structured code review checks for performance regressions and weak tests by evaluating the completed code changes across multiple risk dimensions. It identifies performance issues and testing gaps, then outputs a severity-ordered report with fix directions and merge readiness recommendations.

When should I use risk-based reviewer selection for pull requests?

Use risk-based reviewer selection for pull requests when evaluating pre-merge validation, high-risk surfaces, public API changes, or complex multi-file diffs. It routes the review work to the appropriate specialist for security, correctness, performance, UI, or architecture concerns to ensure merge readiness.