code-review

Review code for architecture, security, performance, and concurrency issues.

Updated Mar 1, 2026
One-click install
npx skills add https://github.com/mqzkim/trading --skill code-review-mqzkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/mqzkim/trading/tree/main/.agents/skills/code-review
Command: npx skills add https://github.com/mqzkim/trading --skill code-review-mqzkim

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the common issue of superficial code reviews by providing an in-depth analysis from the perspective of a seasoned senior architect, identifying critical architectural flaws, security vulnerabilities, and performance bottlenecks that often go unnoticed.

Core Features & Use Cases

  • Deep Architectural Analysis: Evaluates code structure, design patterns, and adherence to architectural principles.
  • Security Vulnerability Detection: Scans for common security risks, including OWASP Top 10 vulnerabilities.
  • Performance Bottleneck Identification: Pinpoints inefficient code, potential performance issues, and scalability concerns.
  • Concurrency and Data Integrity Checks: Assesses risks related to race conditions, deadlocks, and data corruption.
  • Use Case: Review a pull request for a new microservice to ensure it meets security standards, is architecturally sound, and won't introduce performance issues under load.

Quick Start

Use the code-review skill to perform a deep review of the provided GitHub pull request URL.

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 deep code review for architectural and security flaws?

Deep code review evaluates code structure, design patterns, and security risks like OWASP Top 10 vulnerabilities from a senior architect's perspective. It identifies critical architectural flaws, security vulnerabilities, and performance bottlenecks that superficial reviews often miss.

What does a senior architect look for in a backend pull request review?

A senior architect reviews backend pull requests by focusing on architecture, security, performance, concurrency, data integrity, and operational concerns. This approach prioritizes identifying structural flaws and race conditions over superficial style issues.

Can I use this to check for performance bottlenecks and concurrency issues in my code?

Yes, you can use this code review to identify performance bottlenecks and assess concurrency issues. It pinpoints inefficient code, scalability concerns, and risks related to race conditions, deadlocks, and data corruption.

What is the best way to review a microservice pull request for security and scalability?

The best way to review a microservice pull request is through an expert-level analysis that checks for adherence to architectural principles and OWASP security standards. This ensures the service won't introduce performance issues under load.

Why does my code review only catch superficial style issues instead of data integrity risks?

Code reviews often catch only superficial style issues because they lack a senior architect's perspective on data integrity. A deep review assesses architectural principles, operational concerns, and data corruption risks rather than just formatting.