code-reviewer

Identify bugs, security vulnerabilities, performance problems, and maintainability risks in code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code reviews can be inconsistent and time-consuming; this Skill provides a structured, repeatable review that identifies bugs, security issues, performance problems, maintainability risks, and gaps in tests, with severity and actionable fixes.

Core Features & Use Cases

  • Structured findings with type, severity, rationale, and concrete fixes.
  • Applies to evaluating existing code, diffs, or pull requests to generate detailed feedback for developers.
  • Use case: you want a formal review on a PR before merging, or a code health check on a legacy module.

Quick Start

Provide a complete, prioritized code-review with actionable fixes for the supplied code target.

Frequently Asked Questions about code-reviewer

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

FAQPage Schema
How do I get structured code review feedback for a pull request?

Structured code review feedback is generated by analyzing your pull request or code diff to identify bugs, security vulnerabilities, and maintainability risks. It provides a formal review format with severity, rationale, and concrete fix suggestions.

What is included in a formal code review for security vulnerabilities and bugs?

A formal code review includes a structured report with sections for summary, approach, artifacts, validation, and next steps. Findings detail issue type, severity, rationale, and concrete fix suggestions for security vulnerabilities and bugs.

Can I run a code health check on a legacy module to assess maintainability risks?

Yes, you can run a code health check on a legacy module to assess maintainability risks. The review evaluates existing code to identify maintainability issues and test gaps, providing actionable feedback to improve code quality.

Does static analysis for code quality assurance cover performance problems and test gaps?

Yes, static analysis for code quality assurance covers performance problems and test gaps. It evaluates code to identify performance bottlenecks and missing test coverage, generating prioritized findings with severity and actionable fixes.

What's the best way to prioritize code review findings before merging a PR?

The best way to prioritize code review findings is by using the provided severity levels and rationale. The review generates a complete, prioritized list with actionable fixes to address critical bugs and security vulnerabilities before merging.

When should I use an automated code reviewer instead of manual evaluation?

Use an automated code reviewer when manual code reviews become inconsistent and time-consuming. It provides a repeatable review process that identifies bugs, security issues, and performance problems with structured, actionable feedback.