code-review-expert

Review git diffs for SOLID violations, security risks, and reliability concerns.

Updated Aug 23, 2026

Search Tags:#architecture #performance #security #static-analysis #solid #code-review

Ready to run

npx skills add https://github.com/jiakailong/GraphCoder --skill code-review-expert-jiakailong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/jiakailong/GraphCoder/tree/main/app/code_agent/skills/code-review-expert
Command: npx skills add https://github.com/jiakailong/GraphCoder --skill code-review-expert-jiakailong

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a structured, senior-engineer-grade review of the current git changes, identifying design, security, and reliability issues to prevent defects and costly rewrites.

Core Features & Use Cases

SOLID principle checks (SRP, OCP, LSP, ISP, DIP) and architectural guidance for code changes
Security and reliability scans for vulnerabilities, race conditions, data leakage, and misconfigurations
Removal-candidate detection with actionable refactoring plans and safe-guarded changes
Generates severity-based findings and an iterative plan for fixes and verification

Quick Start

Run the Code Review Expert against your latest git changes to generate a prioritized findings report.

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

Review code changes for SOLID violations and security risks by evaluating diffs against established checklists. This process identifies architectural flaws, vulnerabilities, and performance issues, producing severity-scored findings to prevent costly rewrites.

What is static analysis for code review and how does it detect misconfigurations?▼

Static analysis for code review detects misconfigurations and data leakage by scanning source code without execution. It applies security and reliability checks to identify vulnerabilities, race conditions, and architectural issues across pull requests.

How do I check SOLID principles in a pull request before merging?▼

Check SOLID principles in a pull request by applying SRP, OCP, LSP, ISP, and DIP architectural guidance to the diff. This evaluates code changes against design checklists to generate severity-scored findings and an actionable iteration plan.

What is the best way to identify removal candidates and refactoring opportunities in git changes?▼

Identify removal candidates in git changes by analyzing the diff for redundant or unsafe code. This generates a safeguarded refactoring plan and actionable recommendations to improve architecture and eliminate reliability concerns.

Does this code review approach work with raw git diffs and pull requests?▼

Yes, this code review approach works directly with raw git diffs and pull requests. It evaluates the changes by referencing SOLID, security, and code-quality checklists to produce severity-scored findings and an iteration plan.

When should I not use static analysis for detecting race conditions?▼

Static analysis for detecting race conditions has limitations when evaluating complex runtime concurrency behaviors. It excels at identifying architectural and data leakage risks in diffs, but dynamic analysis may be needed for verifying runtime reliability.