code-review-quality

Reviews code for correctness, security, |performance, and maintainability defects with severity classifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual code reviews often miss critical security vulnerabilities, correctness bugs, and performance issues, while wasting time on trivial style nitpicks that do not impact product quality or stability.

Core Features & Use Cases

  • Structured Review Checklist: Covers correctness, security, performance, and maintainability to ensure no high-impact issues are overlooked during reviews.
  • Prioritized Severity Levels: Classifies issues as BLOCK (must fix before merge), SUGGEST (recommended improvement), or NIT (optional style tweak) to streamline feedback and focus on critical fixes.
  • Red Flag Detection: Flags common code smells like multi-responsibility functions, excessive copy-paste duplication, and unhelpful comments to improve long-term code health.
  • Use Case: Use this Skill when reviewing a PR for a new payment processing feature to catch missing input validation, SQL injection risks, and unhandled error cases before merging to production.

Quick Start

Use the code-review-quality skill to review the attached pull request for the new user authentication feature and list all BLOCK and SUGGEST level issues.

Frequently Asked Questions about code-review-quality

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

FAQPage Schema
How do I find security vulnerabilities and bugs during a pull request review?

A pull request review identifies security vulnerabilities and critical bugs by applying a structured checklist that enforces prioritized severity classifications and red flag detection to prevent defects from reaching production.

What is the best way to standardize code review feedback and eliminate style nitpicks?

Standardizing code review feedback requires classifying issues into BLOCK, SUGGEST, or NIT severity levels, which streamlines the process and focuses developer attention on critical fixes rather than trivial style nitpicks.

How does red flag detection improve codebase maintainability?

Red flag detection improves codebase maintainability by identifying common code smells like multi-responsibility functions, excessive copy-paste duplication, and unhelpful comments to ensure long-term code health.

Can I use a structured checklist to audit an existing codebase for performance issues?

Yes, you can use a structured review checklist to audit existing codebases for performance issues, applying prioritized severity levels and red flag detection to standardize quality assessments across legacy software workflows.

When do I need a pre-merge quality check for my software development workflow?

You need a pre-merge quality check when reviewing new features, such as payment processing or user authentication, to catch SQL injection risks, missing input validation, and unhandled error cases before they impact production stability.