code-review-expert

Detect SOLID, security, reliability, performance, and boundary-condition issues in git changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tommy771004/StockAnalyzeAIConnectV2 --skill code-review-expert-tommy771004
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/tommy771004/StockAnalyzeAIConnectV2/tree/main/skills/code-review-expert
Command: npx skills add https://github.com/tommy771004/StockAnalyzeAIConnectV2 --skill code-review-expert-tommy771004

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It helps teams reduce production risk by systematically reviewing recent git changes for design quality (SOLID), security vulnerabilities, reliability issues, performance bottlenecks, and edge-case correctness.

Core Features & Use Cases

  • Structured senior-engineer reviews: Analyzes changes step-by-step across architecture, SOLID principles, dead code/removal candidates, and overall code quality.
  • Security and reliability scanning: Checks for common web/app and runtime risks such as injection, SSRF, auth gaps, secrets leakage, and race conditions.
  • Practical, severity-ranked output: Produces findings labeled by priority (P0–P3) and guides the next action with a review-first workflow.
  • Use Case: When preparing a pull request, use this skill to identify what should block a merge (P0/P1), what should be fixed soon (P2), and what can be deferred (P3).

Quick Start

Run /code-review-expert to review your current git changes and get a prioritized list of findings with suggested fixes.

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 git changes for security vulnerabilities and SOLID principle violations?

Review git changes for security and SOLID violations by analyzing diffs across architecture, reliability, and boundary conditions. This produces severity-ranked findings (P0–P3) to identify merge-blocking issues and guide structured refactoring.

What is the best way to check a pull request for performance bottlenecks and race conditions?

Checking pull requests for performance bottlenecks and race conditions requires scanning runtime risks and edge-case correctness in current git changes. This generates prioritized findings to determine what should block a merge versus what can be fixed later.

Can I use automated code review to detect secrets leakage and injection risks before merging?

Automated code review can detect secrets leakage, injection, and SSRF risks by scanning git diffs. It applies a review-first workflow that categorizes these security vulnerabilities by severity (P0–P3) before implementing any changes.

How to identify dead code and boundary condition issues during iterative refactoring?

Identify dead code and boundary condition issues during refactoring by analyzing current git changes step-by-step. This structured review highlights removal candidates and edge-case correctness problems alongside architecture and design quality flaws.

Does code review work with git diff for code migration and structured engineering reviews?

Code review works with git diff by detecting design, security, and reliability issues in current changes. It suits code migration and iterative refactors, providing a structured engineering review that asks for confirmation before applying fixes.