skills.rest
simplerick0
simplerick0COMMUNITY
Explore all skills by this author →
GitHub

quality-review

Identify and document code quality issues during PR reviews.

Updated Jan 26, 2026
Search Tags:#code quality#readability#maintainability#complexity#review#code-review
One-click install
npx skills add https://github.com/simplerick0/com.ackhax.configs --skill quality-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: quality-review
Source: https://github.com/simplerick0/com.ackhax.configs/tree/main/skills/code-review/quality-review
Command: npx skills add https://github.com/simplerick0/com.ackhax.configs --skill quality-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review code for quality issues during PR reviews, helping teams identify readability, maintainability, and complexity problems early.

Core Features & Use Cases

  • Readability checks: clear naming, consistent formatting, and self-documenting code.
  • Maintainability checks: single responsibility, low coupling, high cohesion, DRY, explicit dependencies, and robust error handling.
  • Complexity checks: cyclomatic complexity, nesting depth, traditional metrics, and class size guidance.
  • Use Case: Apply during PR reviews to surface technical debt and ensure code meets standards before merging.
  • Output: Produce a structured review summary with recommended improvements.

Quick Start

Review the latest changed files in a PR using the quality-review checklist and document findings and suggested fixes.

Frequently Asked Questions about quality-review

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

FAQPage Schema
How do I check code quality issues like readability and maintainability during a PR review?▼

To check code quality during a PR review, assess naming conventions, structure, DRY principles, and cyclomatic complexity. Identifying these readability and maintainability issues early surfaces technical debt and ensures code meets standards before merging.

What metrics should I use to evaluate code complexity in a pull request?▼

Evaluate code complexity in a pull request by measuring cyclomatic complexity and nesting depth. These metrics, along with class size guidance, help identify overly complex code that hinders maintainability and should be refactored before merging.

Can I apply the same code review checklist across different programming languages?▼

Yes, you can apply the code review checklist across different programming languages. It focuses on language-agnostic quality metrics like coupling, cohesion, and error handling, providing structured guidance for any codebase during your PR workflow.

What is the best way to document technical debt found during a code review?▼

The best way to document technical debt found during a code review is to deliver a structured review output. This summary details the identified quality issues and provides recommended improvements for the PR.

Does this code review process check for single responsibility and low coupling?▼

Yes, the code review process checks for single responsibility, low coupling, and high cohesion. It also verifies explicit dependencies and robust error handling to ensure overall code maintainability before the PR is approved.

Related Skills

Explore More Software Engineering Skills→
edobryedobry
6

review-pr

Analyze pull requests and post structured GitHub PR reviews.

Community
Advanced
yalehyaleh
21

Code Refactoring

Refactor Go hotspots to reduce cyclomatic complexity and improve maintainability.

Community
Intermediate
AbeJitsuAbeJitsu

format-standardize

Apply user-defined formatting standards across code, documentation, and content outputs using ESLint and Prettier.

Community
Basic
0xRayAI0xRayAI

project-analysis

Analyze project structure, code complexity, and architectural health with maintainability metrics.

Official
Intermediate