code-review-expert

Analyze git diffs for SOLID violations, security risks, and architectural smells.

Updated Aug 23, 2026

Search Tags:#architecture #security #best-practices #solid #code-review #pull-request

Ready to run

npx skills add https://github.com/JuanGarciaFuture/mobile-practice --skill code-review-expert-juangarciafuture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/JuanGarciaFuture/mobile-practice/tree/main/.cursor/skills/code-review-expert
Command: npx skills add https://github.com/JuanGarciaFuture/mobile-practice --skill code-review-expert-juangarciafuture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, senior-engineer-grade lens to review current git changes for SOLID violations, security risks, and architectural smells, delivering actionable improvements.

Core Features & Use Cases

Detect SOLID violations (SRP, OCP, LSP, ISP, DIP), architecture flaws, and security risks in diffs.
Offer prioritized, concrete remediation suggestions that align with risk levels and project constraints.
Provide a repeatable preflight workflow that guides owners through ownership, critical paths, and potential removal candidates.

Quick Start

Analyze the current diff with a senior engineer lens and request concrete changes in the PR.

Frequently Asked Questions about code-review-expert

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

FAQPage Schema

How do I check my git diff for SOLID violations and security risks?▼

To check your git diff for SOLID violations and security risks, analyze current changes using a senior-engineer lens to surface architectural smells, detect SRP, OCP, LSP, ISP, DIP issues, and provide actionable remediation guidance for pre-merge checks.

What is the best way to perform a senior-level code review on a pull request?▼

The best way to perform a senior-level code review on a pull request is to apply a structured preflight workflow that identifies ownership, critical paths, and potential removal candidates while evaluating maintainability concerns and security findings across codebases.

How do I get actionable remediation suggestions for architectural smells in my codebase?▼

To get actionable remediation suggestions for architectural smells in your codebase, analyze your pull requests and diffs to receive prioritized, concrete improvements that align with risk levels and project constraints based on SOLID focus.

Can I use this approach to detect Single Responsibility Principle violations in current changes?▼

Yes, you can detect Single Responsibility Principle violations in current changes by analyzing the git diff, which explicitly checks for SRP, OCP, LSP, ISP, and DIP violations across codebases to ensure thorough review prompts.

Does code review for security findings require a specific environment setup?▼

Code review for security findings requires applying the analysis to current git changes, pull requests, and diffs across codebases, needing no specific environment setup beyond the standard pre-merge workflow context and ownership guidance.