code-reviewer

Analyze code diffs or PRs and report findings with severity classifications.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/AlexHorovitz/skills --skill code-reviewer-alexhorovitz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/AlexHorovitz/skills/tree/main/code-reviewer
Command: npx skills add https://github.com/AlexHorovitz/skills --skill code-reviewer-alexhorovitz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases often accumulate defects, security gaps, and maintainability issues that slip into production. This Skill provides a rigorous, adversarial review process to catch issues before release and elevate overall software quality.

Core Features & Use Cases

  • Adversarial review mindset: Identify bugs, security vulnerabilities, performance problems, and maintainability smells.
  • PR governance: Audit pull requests and remediation branches with structured findings and remediation guidance.
  • Consistency & standards: Enforce code quality by applying a standardized review framework across languages and stacks.

Quick Start

Provide a high-quality, actionable review by analyzing a given PR and producing a prioritized findings list.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I automate code review for pull requests?

Automate code review for pull requests by analyzing diffs to identify bugs, security vulnerabilities, and performance issues. The process outputs a structured findings report with severity classifications and an optional remediation plan.

What is static analysis for multi-file diffs?

Static analysis for multi-file diffs evaluates cross-file interactions to catch maintainability problems and security gaps. This adversarial review mechanism enforces consistency by applying a standardized framework across common stacks before release.

How do I find security vulnerabilities in a code diff?

Find security vulnerabilities in a code diff through adversarial review that scopes multi-file changes and cross-file interactions. The analysis produces a prioritized findings list classifying issues as BLOCKER or MAJOR for immediate remediation.

Can I review remediation branches across different tech stacks?

Yes, you can review remediation branches across common stacks. The analysis evaluates cross-file interactions and maintains consistency by applying a standardized review framework to identify bugs and maintainability smells regardless of the stack.

What is the best way to enforce quality standards in peer review?

Enforce quality standards in peer review by applying an adversarial review mindset to catch maintainability smells and performance problems. It generates a report with severity classifications like BLOCKER and MINOR to prioritize remediation.

How are code review findings classified and reported?

Code review findings are classified and reported using YAML frontmatter and severity levels: BLOCKER, MAJOR, MINOR, QUESTION, SUGGESTION, and NIT. This structured output provides a prioritized list of bugs and an optional remediation plan.