code-quality-review

Review source code for maintainability, abstraction quality, and branching complexity.

16|1|Updated Jan 2, 2026
One-click install
npx skills add https://github.com/bahayonghang/my-ai-cli-toolkit --skill code-quality-review-bahayonghang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-quality-review
Source: https://github.com/bahayonghang/my-ai-cli-toolkit/tree/main/skills/development-workflows/code-quality-review
Command: npx skills add https://github.com/bahayonghang/my-ai-cli-toolkit --skill code-quality-review-bahayonghang

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill addresses the difficulty of maintaining long-term code health by providing a focused, structural lens to identify maintainability risks, abstraction issues, and architectural regressions before they become technical debt.

Core Features & Use Cases

  • Structural Analysis: Evaluates code for maintainability, abstraction quality, and branching complexity rather than just style or formatting.
  • Evidence-Based Reporting: Generates structured reviews with stable IDs for tracking findings and remediation progress.
  • Use Case: Use this during a pull request review to identify if a new feature introduces unnecessary complexity or violates existing architectural boundaries.

Quick Start

Ask the AI to perform a code quality review on the current changes or a specific file path to receive a structured report on maintainability and structural health.

Frequently Asked Questions about code-quality-review

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

FAQPage Schema
How do I perform a structural code quality review on a pull request?

A structural code quality review evaluates pull request diffs for maintainability and architectural regressions. It generates evidence-based findings with stable tracking IDs to identify abstraction issues and branching complexity before they become technical debt.

What is evidence-based static analysis for code maintainability?

Evidence-based static analysis for code maintainability assesses structural health and architectural risks rather than just code formatting. It generates findings with stable tracking IDs to monitor remediation progress and prevent long-term technical debt.

Can I use this for refactoring planning and diff analysis?

Yes, you can use this for refactoring planning and diff analysis. It performs non-destructive, read-only inspection of source code to pinpoint abstraction issues and complexity regressions, helping you plan structural improvements within your software development lifecycle.

Does the code review process modify my source code files?

No, the code review process does not modify your source code files. It performs a non-destructive, read-only inspection of the codebase to evaluate structural health and identify maintainability risks without altering your original code.

Why does static analysis focus on branching complexity rather than code style?

Static analysis focuses on branching complexity rather than code style to prevent deep architectural regressions. Evaluating structural maintainability and abstraction quality identifies core technical debt risks that surface-level formatting checks consistently miss.