code-review-and-quality

Automates multi-axis code reviews across five quality dimensions before merging.

1|Updated Jan 28, 2025

Search Tags:#architecture #performance #security #quality #code-review #pull-request #review-checklist

Ready to run

npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill code-review-and-quality-josuenavarroaguado

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/josuenavarroaguado/josuenavarroaguado.github.io/tree/main/.github/skills/code-review-and-quality
Command: npx skills add https://github.com/josuenavarroaguado/josuenavarroaguado.github.io --skill code-review-and-quality-josuenavarroaguado

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and accelerates code reviews by providing a structured, multi-axis evaluation before merges, reducing human error and review drift.

Core Features & Use Cases

Five-Axis Evaluation: Assess correctness, readability, architecture, security, and performance for every change.
Approval Gate: Approve only when overall code health improves, not necessarily perfect.
Use Cases: Suitable for PR reviews, refactors, bug fixes, and reviews of AI-generated code.

Quick Start

Review a pull request to initiate a multi-axis evaluation with actionable feedback.

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 automate a multi-axis code review for a pull request?▼

To automate a code review, apply a structured checklist across five axes: correctness, readability, architecture, security, and performance. This process requires severity-labeled feedback and documents resolution status to guide merge decisions.

What is the best way to review AI-generated code before merging?▼

The best way to review AI-generated code is using a standardized multi-axis evaluation. This assesses correctness, readability, architecture, security, and performance, providing severity-labeled feedback to ensure overall code health improves before merging.

Can I use an automated review checklist for bug fixes and feature forks?▼

Yes, you can use an automated review checklist for bug fixes and feature forks. The multi-axis evaluation applies to these changes, imposing structured feedback with severity labels and documented resolution status to standardize the merge process.

Does code review require perfect scores across all axes for an approval gate?▼

No, review approval does not require perfect scores. The approval gate passes when overall code health improves, evaluating correctness, readability, architecture, security, and performance to ensure the change benefits the codebase.

How does severity-labeled feedback work in a structured code review?▼

Severity-labeled feedback in a code review works by assigning priority levels to issues found across correctness, readability, architecture, security, and performance. This documentation tracks resolution status to guide final merge decisions.

When do I need a multi-axis code review instead of a standard check?▼

You need a multi-axis code review when standardizing evaluations to reduce human error and review drift. It is required for pull requests, refactors, and bug fixes to ensure improvements across correctness, security, architecture, performance, and readability.