code-review-and-quality

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code changes often enter main branches without a structured, multi-dimensional review. This Skill provides a formal five-axis framework to evaluate correctness, readability, architecture, security, and performance before merging, reducing defects and rework.

Core Features & Use Cases

  • Five-Axis Review: correctness, readability, architecture, security, and performance.
  • Uses before merging any change, including PRs, feature edits, and bug fixes.
  • Provides a clear approval standard focused on improving overall code health even if the code isn't perfect.

Quick Start

Initiate a five-axis review on a pending pull request to determine if it should be merged.

Frequently Asked Questions about code-review-and-quality

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

FAQPage Schema
What is a multi-axis code review framework?

A multi-axis code review framework evaluates code changes across five distinct criteria: correctness, readability, architecture, security, and performance. This structured approach surfaces quality risks before merging pull requests, reducing defects and rework.

How do I review a pull request for architecture and security risks?

You can review a pull request for architecture and security risks by applying a five-axis framework that explicitly tests code changes against correctness, readability, architecture, security, and performance criteria before reaching an approval decision.

When do I need to use a structured code review process?

You need a structured code review process before merging any code changes into main branches, including feature edits, bug fixes, and pull requests. Applying multi-dimensional criteria ensures healthier code and reduces post-merge defects.

What's the best way to evaluate code quality before merging?

The best way to evaluate code quality before merging is to rigorously assess changes across five axes: correctness, readability, architecture, security, and performance. This provides a clear approval standard focused on improving overall code health.

Does a formal code review framework require perfect code to approve a pull request?

A formal code review framework does not require perfect code to approve a pull request. It uses explicit criteria across five axes to provide a clear approval standard focused on improving overall code health even if the code isn't perfect.