code-review

Name: code-review
Availability: InStock
Author: Andrew

Review code changes against a base branch for maintainability and structural issues.

2|Updated Jun 19, 2026

Search Tags:#architecture #code review #refactoring #maintainability #abstraction #spaghetti code

Ready to run

npx skills add https://github.com/andrewthetechie/andrew-skills --skill code-review-andrewthetechie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/andrewthetechie/andrew-skills/tree/main/code-review
Command: npx skills add https://github.com/andrewthetechie/andrew-skills --skill code-review-andrewthetechie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps reviewers perform a very strict code quality audit focused on maintainability, structural simplification, abstraction quality, and avoiding spaghetti growth in diffs.

Core Features & Use Cases

Thermonuclear maintainability review: Flags structural regressions, unnecessary complexity, and design debt.
Architecture scrutiny: Evaluates file size growth, coupling, boundary leaks, wrapper abuse, and awkward control flow.
Use case: Review a pull request against a base branch and identify where the implementation should be simplified, decomposed, or moved to a better layer.

Quick Start

Review this branch against main and call out any maintainability regressions.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I review a pull request for maintainability and architecture issues?▼

To review a pull request for maintainability, you can audit the diff against a base branch to flag structural regressions, unnecessary complexity, and design debt. This process evaluates abstraction quality and identifies where implementation should be simplified or decomposed.

What is the best way to catch spaghetti code and coupling in a branch diff?▼

Catching spaghetti code in a branch diff requires architecture scrutiny that evaluates file size growth, boundary leaks, wrapper abuse, and awkward control flow. This strict review flags structural regressions and design debt before merging changes.

Can I use a code review tool to check abstraction quality and refactoring needs?▼

Yes, you can use a code review tool to check abstraction quality by applying structural scrutiny to pull requests. It identifies awkward control flow and wrapper abuse, highlighting exactly where the implementation should be simplified or moved to a better layer.

Does maintainability review work without specifying a base branch or commit range?▼

Maintainability review does not work without comparison context. It requires a specified base branch, commit, or base range to perform the diff comparison needed to judge code quality and identify structural regressions.

How do I identify design debt and unnecessary complexity in a diff?▼

You identify design debt and unnecessary complexity by performing an aggressive maintainability audit on the code changes. This review targets structural simplification and abstraction quality, flagging awkward control flow and wrapper abuse in the diff.