code-review

Review pull requests across architecture, logic, and edge-case hardening.

16|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/antgroup/Agent3Sigma-Stage --skill code-review-antgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/antgroup/Agent3Sigma-Stage/tree/main/data/advance/skill_templates/Document_Review/benign_skills/wpank_code-review
Command: npx skills add https://github.com/antgroup/Agent3Sigma-Stage --skill code-review-antgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the inconsistency and oversight common in manual code reviews by providing a structured, multi-pass framework that ensures security, performance, and maintainability standards are met for every pull request.

Core Features & Use Cases

  • Multi-Pass Review Process: Guides the reviewer through high-level architecture, line-by-line logic, and edge-case hardening.
  • Comprehensive Checklists: Includes specific criteria for security (SQLi, XSS, Auth), performance (N+1, memory leaks), and maintainability.
  • Severity-Based Feedback: Standardizes communication with clear labels (Critical, Major, Minor, Nitpick) to define merge-blocking issues.
  • Use Case: Use this Skill when auditing a complex pull request to ensure no security vulnerabilities or performance bottlenecks are missed before merging into the main branch.

Quick Start

Use the code-review skill to perform a three-pass analysis on the current pull request diff and provide feedback with severity labels.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a systematic code review on a pull request?

A systematic code review uses a multi-pass framework to evaluate pull requests, guiding reviewers through high-level architecture, line-by-line logic, and edge-case hardening.

What is the best way to standardize pull request feedback for merge-blocking issues?

Standardize pull request feedback by applying severity-based labels like Critical, Major, Minor, and Nitpick to clearly define which code quality or security issues block merging.

How can I detect security vulnerabilities and performance bottlenecks during code reviews?

Detect security vulnerabilities and performance bottlenecks by applying comprehensive review checklists targeting issues like SQLi, XSS, N+1 queries, and memory leaks.

Does this multi-pass code review approach work for maintaining architectural consistency?

Yes, the multi-pass code review process works for maintaining architectural consistency by systematically evaluating software quality and maintainability standards in every pull request.

What are the limitations of manual code reviews compared to a structured framework?

Manual code reviews suffer from inconsistency and oversight, whereas a structured framework enforces security, performance, and maintainability standards to prevent missed vulnerabilities.