code-reviewer

Analyze git pull requests for security vulnerabilities and SOLID violations.

Updated Nov 3, 2016
One-click install
npx skills add https://github.com/xleliberty/mydotfiles --skill code-reviewer-xleliberty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/xleliberty/mydotfiles/tree/main/.config/.claude/plugins/cache/claude-code-skills/engineering-skills/2.1.2/code-reviewer
Command: npx skills add https://github.com/xleliberty/mydotfiles --skill code-reviewer-xleliberty

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the tedious and error-prone process of reviewing pull requests, helping teams maintain high code quality, security, and consistency without manual overhead.

Core Features & Use Cases

  • PR Analysis: Automatically assesses git diffs to identify security risks, complexity, and potential bugs before they reach production.
  • Code Quality Checks: Scans source code for SOLID violations, code smells, and structural issues like god classes or deep nesting.
  • Use Case: Use this tool to generate a comprehensive review report for a large pull request, ensuring that security vulnerabilities like SQL injection or hardcoded secrets are caught early.

Quick Start

Run the code reviewer on the current directory to generate a full quality report and identify potential code smells.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate pull request analysis for security vulnerabilities and code smells?

Automating pull request analysis scans git diffs to identify security vulnerabilities, structural code smells, and SOLID principle violations. It automatically assesses source code complexity to catch risks before they reach production.

What is the best way to enforce coding standards and prioritize technical debt in a git repository?

The best way to enforce coding standards is running automated static analysis on the git repository. This generates a structured review report that identifies technical debt and enforces quality standards across multiple programming languages.

Can I detect hardcoded secrets and SQL injection risks before merging a pull request?

Yes, automated code review detects hardcoded secrets and SQL injection risks by analyzing pull request diffs. It catches security vulnerabilities early, ensuring high code quality and consistency before changes are merged.

Does automated static analysis work for multiple programming languages or just a single codebase?

Automated static analysis works for multiple programming languages, scanning source code to identify structural issues. It assesses git repositories regardless of the specific language to enforce consistent quality standards.

How do I generate a comprehensive code quality report for a large pull request?

To generate a code quality report, run the code reviewer on the current directory. It analyzes the pull request diff to produce a structured report highlighting security vulnerabilities, complexity, and potential bugs.