code-review-expert

Name: code-review-expert
Availability: InStock
Author: omarrohit20

Identify and remediate SOLID, security, and reliability issues in git changes.

Updated Dec 12, 2025

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

Ready to run

npx skills add https://github.com/omarrohit20/ui_automation --skill code-review-expert-omarrohit20

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/omarrohit20/ui_automation/tree/main/.agents/skills/code-review-expert
Command: npx skills add https://github.com/omarrohit20/ui_automation --skill code-review-expert-omarrohit20

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Structured, high-signal code reviews of git changes using a senior engineer lens to surface SOLID violations, architecture concerns, and security risks, with actionable improvements.

Core Features & Use Cases

Preflight context extraction: identify entry points, ownership boundaries, and critical paths in changes.
SOLID + architecture checks: detect SRP, OCP, LSP, ISP, and DIP smells and guide safe refactors.
Removal candidates + iteration planning: surface dead code or risky changes with a concrete migration path.
Security & reliability scans: surface auth, input validation, dependency risks, and runtime reliability issues.

Quick Start

Run a local diff, review changes against SOLID, security, and reliability checklists, and propose concrete, testable improvements.

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 pull requests for SOLID violations and security risks?▼

Review pull requests for SOLID violations and security risks by analyzing git diffs against established architecture and security checklists. This process surfaces SRP, OCP, LSP, ISP, and DIP smells while detecting input validation and auth issues before merge.

What is the best way to find refactoring candidates in a git diff?▼

The best way to find refactoring candidates in a git diff is to perform a senior-level code review that identifies dead code and risky changes. This approach generates a concrete removal plan and migration path to guide safe refactors.

Does this code review approach work with both front-end and back-end codebases?▼

Yes, this code review approach works with both front-end and back-end codebases. It applies SOLID checks, security scans, and reliability analysis universally across recent git changes to identify blocking defects regardless of the stack.

How do I check my code changes against security and reliability checklists?▼

Check code changes against security and reliability checklists by running a structured review on your recent git diff. This surfaces authentication flaws, input validation gaps, dependency risks, and runtime reliability issues with actionable improvements.

When do I need a preflight context extraction for code review?▼

You need a preflight context extraction for code review when analyzing complex pull requests. It identifies entry points, ownership boundaries, and critical paths in recent git changes to prioritize blocking defects before merge.