skills.rest
Rosetears520
Rosetears520COMMUNITY
Explore all skills by this author →
GitHub

code-review-and-quality

Review pull requests across correctness, readability, architecture, security, and performance.

2|Updated May 3, 2026
Search Tags:#testing#architecture#code review#performance#security#readability#quality gates
One-click install
npx skills add https://github.com/Rosetears520/aili-workflows --skill code-review-and-quality-rosetears520
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/Rosetears520/aili-workflows/tree/main/skills/code-review-and-quality
Command: npx skills add https://github.com/Rosetears520/aili-workflows --skill code-review-and-quality-rosetears520

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps teams catch correctness bugs, risky design choices, readability issues, security vulnerabilities, and performance regressions before code lands on the main branch.

Core Features & Use Cases

  • Five-axis review (correctness, readability, architecture, security, performance) with a consistent quality-gate rubric for every change.
  • Change sizing and splitting guidance to keep reviews focused and avoid “too big to review” merges.
  • Structured review process that prioritizes context, then tests, then implementation, and ends with evidence-backed verdicts.
  • Severity-labeled findings (Critical/Required/Nit/Optional/FYI) so authors know what must be fixed before merging.
  • Verification and stress-test steps to prevent unverified conclusions from becoming merge approvals.
  • Multi-model review pattern and honesty rules to reduce blind spots and avoid rubber-stamping.

Quick Start

Use this skill to review a proposed pull request and produce a five-axis assessment with severity-labeled findings, a verification checklist, and an evidence-backed verdict.

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 review a pull request for security vulnerabilities and performance regressions before merging?▼

Review a pull request by applying a five-axis rubric covering correctness, security, performance, architecture, and readability. This structured code review process prevents risky changes from merging by requiring test-first context and producing severity-labeled findings with evidence-backed verdicts.

What is a five-axis code review and when do I need it for my codebase?▼

A five-axis code review evaluates changes across correctness, readability, architecture, security, and performance using a consistent quality-gate rubric. You need this process during pre-merge pull request reviews, refactors, bug fixes, and when evaluating AI-generated code to prevent insecure or poorly architected changes from landing on the main branch.

Can I use automated quality gates to review AI-generated code safely?▼

Yes, automated quality gates can review AI-generated code by applying a five-axis rubric with severity-labeled findings. The process enforces test-first context, verification steps, and an evidence-based stress-test to prevent unverified conclusions from becoming merge approvals, reducing blind spots common in agent-generated changes.

What's the best way to handle pull requests that are too big to review effectively?▼

The best way to handle oversized pull requests is to use change sizing and splitting guidance provided during the review process. This keeps reviews focused and ensures every change satisfies the five-axis quality-gate rubric, avoiding the risks of merging large, unverified code blocks without proper architectural or security assessment.

Why does my code review process fail to catch correctness bugs before they reach the main branch?▼

Code review processes fail to catch correctness bugs when they lack test-first context, structured verification, and an evidence-based stress-test for remaining gaps. Applying a five-axis rubric with severity-labeled findings and multi-model review patterns prevents unverified conclusions from becoming rubber-stamped merge approvals.

Related Skills

Explore More Software Engineering Skills→
loianeloiane
50

spring-security-baseline

Establish a secure Spring Security baseline for Spring Boot 7 applications.

Community
Intermediate
buYoungbuYoung
18

code-review

Review git changes for defects, security gaps, and breaking changes.

Community
Advanced
ayeshakhalid192007-devayeshakhalid192007-dev
1

code-analyzer

Analyze codebases for security, performance, and maintainability issues across files and dependencies.

Community
Advanced
harishgovardhandamodarharishgovardhandamodar

code-review-and-quality

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

Community
Advanced