code-review-and-quality

Review code changes across correctness, readability, architecture, security, and performance.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/yolo-labs-hq/yolo-skills-registry --skill code-review-and-quality-yolo-labs-hq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/yolo-labs-hq/yolo-skills-registry/tree/main/skills/code-review-and-quality
Command: npx skills add https://github.com/yolo-labs-hq/yolo-skills-registry --skill code-review-and-quality-yolo-labs-hq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conducts multi-axis code review to ensure changes improve overall code health before merging, balancing correctness, readability, architecture, security, and performance.

Core Features & Use Cases

  • Five-axis evaluation: checks correctness, readability, architecture, security, and performance for any code change.
  • Guardrails for merges: provides structured feedback to prevent regression and debt.
  • Use Case: Before merging a PR, run the review to verify edge cases, test coverage, and security checks.

Quick Start

Initiate a review by evaluating the latest changes across all five axes and provide structured, actionable feedback to the author.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
How do I perform a structured code review before merging changes?

Perform a structured code review by evaluating the latest changes across five axes: correctness, readability, architecture, security, and performance. It requires clear findings, documentation, and categorization of issues by severity to provide actionable feedback.

What is multi-axis code review and how does it balance code quality?

Multi-axis code review is a process assessing code changes across correctness, readability, architecture, security, and performance to balance overall code health. It ensures changes improve the codebase and prevents regression and debt before merging.

Can I use automated code review for changes written by an AI agent or human?

Yes, you can use automated code review for changes written by an AI agent or a human. The five-axis assessment applies regardless of the author, verifying edge cases, test coverage, and security checks before merging.

What's the best way to enforce guardrails for merges and prevent technical debt?

The best way to enforce guardrails for merges is to run a structured five-axis review that evaluates correctness, readability, architecture, security, and performance. It provides structured feedback to prevent regression and debt.

Does multi-axis code review check for security vulnerabilities and performance issues?

Yes, multi-axis code review checks for security vulnerabilities and performance issues. Security and performance are two of the five axes evaluated during the review process, ensuring all changes are verified before merging.

When do I need to categorize code review issues by severity?

You need to categorize code review issues by severity when conducting a structured five-axis assessment. This categorization ensures clear findings and documentation, providing actionable feedback to the author before merging.