code-reviewer

Identify code-quality issues in PRs with severity-labeled findings and fixes.

9|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/e-t-y-b/etyb-skills --skill code-reviewer-e-t-y-b
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-reviewer
Source: https://github.com/e-t-y-b/etyb-skills/tree/main/skills/code-reviewer
Command: npx skills add https://github.com/e-t-y-b/etyb-skills --skill code-reviewer-e-t-y-b

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Code-reviewer provides expert feedback across quality, performance, security, and architecture to help reviewers issue precise, actionable recommendations on PRs, diffs, or audits.

Core Features & Use Cases

  • Systematic evaluation across four dimensions: quality, performance, security, and architecture.
  • Prioritized, severity-based findings with clear fixes and examples for developers.
  • Ideal for PR reviews, design audits, and policy-compliance checks in codebases of any size.

Quick Start

Review a PR and generate a structured, prioritized feedback report across quality, performance, security, and architecture.

Frequently Asked Questions about code-reviewer

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

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

To get actionable code review feedback, evaluate your pull request across code quality, performance, security, and architecture. This process generates severity-labeled findings with concrete fixes, references, and a completion checklist to guide developers.

What is the best way to review code quality and security in a PR diff?

The best way to review code quality and security in a PR diff is to systematically enforce evaluation across four dimensions: quality, performance, security, and architecture. This produces prioritized, severity-based findings with clear fixes and examples.

Does this code review approach work across different programming languages and architectures?

Yes, this code review approach works across different programming languages and architectures. It systematically evaluates diffs and PRs to identify code-quality issues, enforcing performance and security checks regardless of the specific tech stack.

How do I enforce security and performance checks during a code review?

You enforce security and performance checks during a code review by applying a systematic evaluation framework. It identifies vulnerabilities and performance anti-patterns, outputting severity-labeled findings with concrete fixes and references for developers.

Can I use this for design audits and policy-compliance checks in my codebase?

Yes, you can use this for design audits and policy-compliance checks in codebases of any size. It evaluates architecture and quality dimensions to provide expert feedback and structured, prioritized recommendations.

Why should I use a structured code review process instead of ad-hoc PR comments?

A structured code review process ensures systematic evaluation across quality, performance, security, and architecture. Unlike ad-hoc comments, it outputs prioritized, severity-based findings with concrete fixes, examples, and a completion checklist for comprehensive coverage.