code-review-expert

Analyze latest git changes for SOLID violations and security risks.

Updated Feb 5, 2026
One-click install
npx skills add https://github.com/SHINZO111/llm-smart-router --skill code-review-expert-shinzo111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/SHINZO111/llm-smart-router/tree/main/.claude/skills/code-review-expert
Command: npx skills add https://github.com/SHINZO111/llm-smart-router --skill code-review-expert-shinzo111

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables teams to rapidly and thoroughly review code changes by detecting SOLID violations, architecture concerns, removal candidates, and security risks, delivering actionable improvements.

Core Features & Use Cases

  • Structured review of the latest git changes focused on SOLID principles, maintainability, and architectural clarity.
  • Risk-grade outputs with severity levels (P0-P3) and concrete remediation steps for each finding.
  • Removal candidates & security scans to surface dead code, anti-patterns, and potential vulnerabilities with recommended next steps.
  • Use Case: When reviewing a PR, the skill highlights violations and proposes precise refactors or alternative designs to unblock merge while preserving behavior.

Quick Start

Provide the diff or PR summary to the skill and request a structured review. The skill will return findings with severities, suggested fixes, and a plan for refactoring if needed.

Frequently Asked Questions about code-review-expert

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

FAQPage Schema
How do I identify SOLID violations and security risks in a pull request?

Code review for pull requests identifies SOLID violations, security risks, and architecture concerns by analyzing the latest git changes. It applies structured preflight, security scans, and SOLID checks across languages to deliver actionable fixes.

How do I get actionable refactoring suggestions during a code review?

To get actionable refactoring suggestions during a code review, provide the diff or PR summary. The review highlights violations and proposes precise refactors or alternative designs to unblock merge while preserving behavior.

Can I use static analysis to find dead code and removal candidates across different programming languages?

Yes, static analysis for code review works across languages to surface removal candidates and dead code. It identifies anti-patterns and potential vulnerabilities, recommending next steps for maintainability.

What is the best way to prioritize code review findings for architecture and maintainability?

The best way to prioritize code review findings is using a severity workflow from P0 to P3. This risk-grade output categorizes architecture and maintainability issues with concrete remediation steps for each finding.

Does code review for git changes require a specific static analysis dependency?

No dependencies are required for this code review of git changes. It operates independently to analyze diffs and PR summaries for SOLID violations and security risks without external static analysis tools.