Code Review Expert

Review pull requests for logic, security, and architecture issues.

Updated Mar 7, 2026

Search Tags:#quality assurance #code review #best practices #pull request #security #software development

Ready to run

npx skills add https://github.com/ntluong95/agent-skills-statistics --skill code-review-expert-ntluong95

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Code Review Expert
Source: https://github.com/ntluong95/agent-skills-statistics/tree/main/.github/skills/common/code-review
Command: npx skills add https://github.com/ntluong95/agent-skills-statistics --skill code-review-expert-ntluong95

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured and persona-driven approach to code reviews, ensuring higher quality, more secure, and more maintainable code by focusing on critical aspects beyond superficial style.

Core Features & Use Cases

Persona-Driven Reviews: Adopts a Principal Engineer mindset to focus on logic, security, and architecture.
Constructive Feedback: Prioritizes questions over commands and categorizes feedback for clarity.
Comprehensive Checklist: Guides reviewers through security, performance, correctness, and clean code principles.
Use Case: When reviewing a Pull Request, use this Skill to ensure all security vulnerabilities are identified, performance bottlenecks are addressed, and the code adheres to SOLID principles before merging.

Quick Start

Use the Code Review Expert skill to review the attached code changes for security vulnerabilities and logic errors.

Frequently Asked Questions about Code Review Expert

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

FAQPage Schema

What should a high-quality code review focus on beyond coding style?▼

A high-quality code review should focus on logic correctness, security vulnerabilities, architecture adherence, and performance optimization rather than superficial style, enforcing input sanitization and clean code principles.

How do I review a pull request for security vulnerabilities and logic errors?▼

To review a pull request for security vulnerabilities and logic errors, apply a structured checklist that validates input sanitization, verifies performance bottlenecks, and checks architecture against clean code practices. Categorize feedback to ensure constructive team communication.

How do I provide constructive code review feedback to my team?▼

Provide constructive code review feedback by adopting a Principal Engineer mindset that prioritizes questions over commands. Categorize feedback into security, performance, correctness, and clean code sections to deliver clear, actionable insights for team improvements.

Does this code review approach work for analyzing changes before merging?▼

Yes, this code review approach works specifically for analyzing changes before merging by validating adherence to SOLID principles, identifying security vulnerabilities, and addressing performance bottlenecks to ensure high-quality pull request integration.

When do I need a comprehensive code review checklist?▼

You need a comprehensive code review checklist when reviewing pull requests to ensure no critical issues are missed. It guides reviewers through security, performance, correctness, and clean code principles to guarantee thorough quality assurance before merging.