code-review

Review code changes with structured checklists across security, performance, correctness, maintainability, and testing.

4|1|Updated Mar 14, 2026
One-click install
npx skills add https://github.com/GPTtang/skill-atlas --skill code-review-gpttang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/GPTtang/skill-atlas/tree/main/skills/devops/code-review
Command: npx skills add https://github.com/GPTtang/skill-atlas --skill code-review-gpttang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive and systematic approach to code reviews, ensuring higher code quality, security, and maintainability by identifying potential issues across various dimensions.

Core Features & Use Cases

  • Structured Checklists: Detailed checklists for Security, Performance, Correctness, Maintainability, and Testing.
  • Severity Levels: Clear classification of feedback (Critical, Major, Minor, Nitpick) to prioritize actions.
  • Review Process Guidance: A three-pass review strategy to ensure thoroughness.
  • Use Case: When reviewing a Pull Request, use this Skill to ensure all critical security checks are performed and to provide structured, actionable feedback to the author.

Quick Start

Use the code-review skill to systematically review the attached code changes.

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 for a pull request?

A systematic code review uses a three-pass process with structured checklists covering security, performance, correctness, maintainability, and testing. This approach ensures thorough evaluation of code changes and provides prioritized, actionable feedback to the author.

What severity levels should I use to prioritize code review feedback?

Code review feedback severity levels are categorized as Critical, Major, Minor, and Nitpick. This classification helps reviewers prioritize actions and ensures authors address the most significant security and performance issues first.

What is the best way to check code security and maintainability during reviews?

The best way to check security and maintainability is using detailed review checklists. These checklists guide reviewers to identify potential vulnerabilities and structural issues, ensuring higher code quality and robust software engineering standards.

Does a structured code review process work for establishing team review standards?

Yes, a structured code review process works for establishing review standards by defining consistent severity levels and multi-pass evaluation steps. It ensures all critical security and testing dimensions are uniformly assessed across the team.

What dimensions should a comprehensive code quality checklist include?

A comprehensive code quality checklist should include security, performance, correctness, maintainability, and testing dimensions. Evaluating these specific areas ensures the systematic identification of potential issues and improves overall code stability.