code-review-expert

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

17|1|Updated Apr 20, 2022
One-click install
npx skills add https://github.com/jvegaf/harmony --skill code-review-expert-jvegaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-expert
Source: https://github.com/jvegaf/harmony/tree/main/.agents/skills/code-review-expert
Command: npx skills add https://github.com/jvegaf/harmony --skill code-review-expert-jvegaf

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of performing in-depth code reviews, identifying critical issues like SOLID violations, security risks, and performance bottlenecks, which are often missed in manual reviews.

Core Features & Use Cases

  • Comprehensive Code Analysis: Analyzes git changes for adherence to SOLID principles, architectural smells, potential security vulnerabilities, and reliability concerns.
  • Actionable Feedback: Provides detailed findings categorized by severity (P0-P3) and suggests concrete improvements or refactoring plans.
  • Use Case: Before merging a new feature, submit your code changes to this Skill to receive a senior engineer's review, ensuring code quality, security, and maintainability.

Quick Start

Review the current git changes for SOLID violations, security risks, and performance issues.

Frequently Asked Questions about code-review-expert

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

FAQPage Schema
How do I automate code review for git changes to catch security vulnerabilities?

Automating code review for git changes involves analyzing diffs for security vulnerabilities, SOLID violations, and race conditions. It provides actionable feedback with severity levels to ensure code reliability before merging.

What is a senior engineer code review checklist for SOLID principles and performance?

A senior engineer code review checklist for SOLID principles and performance evaluates architectural smells, boundary condition bugs, and error handling. It categorizes findings by severity to suggest concrete refactoring improvements.

How do I find race conditions and boundary bugs in my git diff before merging?

Find race conditions and boundary bugs in your git diff by submitting changes for expert code analysis. The review identifies reliability concerns and provides structured, actionable feedback to prevent runtime errors.

Does automated code review work for complex refactoring and architectural smells?

Automated code review works for complex refactoring and architectural smells by checking adherence to SOLID principles. It identifies structural issues and suggests concrete improvement plans to maintain code quality.

What is the best way to categorize code review findings by severity?

The best way to categorize code review findings by severity is using a structured P0-P3 scale. This prioritizes critical security vulnerabilities and performance bottlenecks over minor refactoring suggestions for actionable feedback.