code-review-and-quality

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

9|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/klh/speedy-claude --skill code-review-and-quality-klh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-review-and-quality
Source: https://github.com/klh/speedy-claude/tree/main/skills/code-review-and-quality
Command: npx skills add https://github.com/klh/speedy-claude --skill code-review-and-quality-klh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull requests and code changes often merge with hidden defects, inconsistent style, security regressions, or performance regressions because reviews focus on limited signals or skip critical axes; this Skill provides a structured, multi-dimensional review process to catch those issues before merge and to raise clear, prioritized feedback.

Core Features & Use Cases

  • Five-axis review: Evaluates correctness, readability & simplicity, architecture, security, and performance for every change.
  • Checklist-driven findings with severity labels: Produces categorized comments marked as Critical, Required, Optional, or Nit to clarify required actions versus suggestions.
  • Verification & change sizing: Confirms tests, build status, and verification stories; recommends split strategies for oversized changes.
  • Use case: Review a bugfix, a refactor, or agent-generated code to ensure it matches the spec, includes adequate tests, and does not introduce security or performance regressions.

Quick Start

Review the pull request for correctness, readability, architecture, security, and performance and return a checklist-driven verdict with categorized findings and severity labels.

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 comprehensive code review before merging a pull request?

A comprehensive code review evaluates pull requests across correctness, readability, architecture, security, and performance. It uses a checklist-driven process to produce categorized findings with severity labels, ensuring no critical axis is skipped before merge.

What is the best way to review agent-generated code for security and performance regressions?

Reviewing agent-generated code requires a multi-axis evaluation covering security and performance alongside correctness. A structured review process validates tests and build status, returning a checklist-driven verdict with actionable recommendations and severity labels.

How do I prioritize feedback and split oversized pull requests during a code review?

To prioritize feedback, categorize findings using severity labels like Critical, Required, Optional, and Nit. For oversized changes, the review process recommends split strategies and verifies test coverage to ensure manageable, safe merges.

Does multi-axis code review work for bug fixes and refactoring tasks?

Multi-axis code review applies directly to bug fixes and refactoring tasks. It evaluates whether the changes match specifications, confirms adequate tests are included, and ensures no new security or performance regressions are introduced.

Why does my pull request merge with hidden defects despite having a review process?

Hidden defects often merge when reviews focus on limited signals or skip critical axes like architecture and security. A structured, multi-dimensional review process catches these missed issues by enforcing a comprehensive five-axis evaluation before merging.

When should I not use an automated checklist-driven code review?

Checklist-driven code review is designed for pull requests, refactors, and agent-generated code. It may be unnecessary for trivial style-only changes or documentation updates where security, performance, and architectural regressions are not a concern.