code-review-expert

Review current git changes and output P0–P3 severity findings.

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/ToanPV90/dotfiles --skill code-review-expert-toanpv90
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/ToanPV90/dotfiles/tree/main/agents/.agents/skills/code-review-expert
Command: npx skills add https://github.com/ToanPV90/dotfiles --skill code-review-expert-toanpv90

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code Review Expert helps you catch maintainability, security, and reliability issues in your proposed changes before they ship, by turning a raw git diff into a structured, severity-ranked review.

Core Features & Use Cases

  • SOLID + Architecture Review: Flags SRP/OCP/LSP/ISP/DIP smells and architecture weaknesses, then suggests safer refactor directions.
  • Removal/Iteration Planning: Identifies dead or redundant code and proposes a safe deletion strategy (or a deferred plan with checkpoints).
  • Security & Reliability Scan: Checks for common security risks (injection, SSRF, path traversal, secrets leakage) and reliability hazards (race conditions, unbounded loops, unsafe defaults).
  • Code Quality Checks: Surfaces error-handling gaps, performance issues (e.g., N+1 patterns), and boundary-condition bugs.

Quick Start

Ask your agent to run /code-review-expert to review your current git changes and produce a P0–P3 severity report without implementing changes automatically.

Frequently Asked Questions about code-review-expert

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

FAQPage Schema
How do I review my git diff for security and reliability risks?

To review your git diff for security and reliability risks, this tool scans your current changes to identify injection flaws, race conditions, and unbounded loops, then outputs a structured report with P0–P3 severity rankings. It checks for common hazards without modifying your code automatically.

What's the best way to detect SOLID principle violations in uncommitted code?

Detecting SOLID principle violations in uncommitted code requires analyzing your git changes against SRP, OCP, LSP, ISP, and DIP criteria. This review process flags architectural smells and proposes safer refactoring directions to improve maintainability before merging.

Can I use a pre-merge code review to find performance issues like N+1 queries?

Yes, you can use a pre-merge code review to find performance issues like N+1 query patterns. By processing your git status and diff, the review surfaces boundary-condition bugs and error-handling gaps, providing actionable improvements for your proposed changes.

How do I plan safe deletion of dead code found during a security audit?

To plan the safe deletion of dead code found during a security audit, the review identifies redundant code and proposes a structured removal strategy. It can also suggest a deferred iteration plan with checkpoints to ensure reliability throughout the refactoring process.