code-review-expert

Review current git changes for SOLID violations, security risks, and improvements.

5.0k|548|Updated May 14, 2025
One-click install
npx skills add https://github.com/dtyq/magic --skill code-review-expert-dtyq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/dtyq/magic/tree/main/frontend/magic-web/.agents/skills/code-review-expert
Command: npx skills add https://github.com/dtyq/magic --skill code-review-expert-dtyq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill enables structured, senior-engineer style reviews of current git changes, identifying SOLID violations, security risks, and actionable improvements to raise code quality and maintainability.

Core Features & Use Cases

  • Preflight and scoping: analyzes git status -sb, git diff --stat, and git diff to define the changes under review and identify ownership boundaries.
  • SOLID & architecture checks: leverages a formal checklist to surface SRP, OCP, LSP, ISP, and DIP smells, with guidance for safe refactors and extension points.
  • Removal candidates and iteration: spots dead or risky code for safe removal or staged deprecation with explicit follow-up plans.
  • Security & reliability scanning: assesses for common vulnerabilities, authZ/authN gaps, secret leakage, and runtime risks with remediation guidance.
  • Code quality evaluation: evaluates error handling, performance, boundary conditions, and testing coverage, offering concrete improvement suggestions.
  • Structured output: produces findings with severity levels, inline comment formats, and a clear next-steps plan for teams.

Quick Start

Review the current git changes and provide a structured critique focusing on SOLID, architecture, security risks, and actionable 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 a pull request for SOLID violations and security risks?

To review a pull request for SOLID violations and security risks, apply a senior engineer lens to analyze git diffs, detect architecture smells, and surface vulnerabilities with structured severity scoring and explicit remediation guidance.

What is the best way to scan git changes for code quality and maintainability issues?

Scanning git changes for code quality and maintainability issues is best done by evaluating error handling, boundary conditions, and testing coverage, while spotting dead code candidates for safe removal or staged deprecation with follow-up plans.

How do I check my code diff for security vulnerabilities and secret leakage before merging?

Checking your code diff for security vulnerabilities and secret leakage involves assessing authN/authZ gaps and runtime risks using a structured workflow, providing inline comment formats and remediation guidance to protect your project.

Does this code review approach work without configuring external dependencies or linters?

This code review approach works without external dependencies, relying on a preflight scoping mechanism that analyzes git status and diff outputs to define changes and identify ownership boundaries natively.

How do I identify safe refactoring points for SRP and OCP smells in my current pull request?

To identify safe refactoring points for SRP and OCP smells in your pull request, leverage a formal architecture checklist to surface violations and generate guidance for safe refactors and extension points.