skills.rest
rob-broadley
rob-broadleyCOMMUNITY
Explore all skills by this author →
GitHub

code-review

Review code diffs for correctness, maintainability, and severity-graded findings.

Updated May 10, 2026
Search Tags:#static analysis#code review#maintainability#complexity#test coverage#dead code#severity model
One-click install
npx skills add https://github.com/rob-broadley/ai-airbase --skill code-review-rob-broadley
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: code-review
Source: https://github.com/rob-broadley/ai-airbase/tree/main/cadre/skills/code-review
Command: npx skills add https://github.com/rob-broadley/ai-airbase --skill code-review-rob-broadley

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you systematically evaluate code changes for correctness, maintainability, and fit for purpose while prioritizing fixes by severity.

Core Features & Use Cases

  • Structured review coverage: Examines architecture, naming quality, complexity, coupling, test/documentation gaps, and dead code signals.
  • Smell-driven inspection: Guides detection across bloaters, change preventers, couplers, dispensables, and OO-abuse categories.
  • Severity-first outputs: Produces findings graded into Blocking, Recommendation, and Observation so the highest-impact issues get addressed first.
  • Scope clarity: Avoids duplicating other design-signal skills by focusing on review mechanics while pointing to companion guidance for SOLID/GRASP.

Quick Start

Use the code-review skill to review a proposed diff by producing findings grouped by severity, covering structure, naming, complexity, coupling, test and documentation gaps, and dead code signals.

Frequently Asked Questions about code-review

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

FAQPage Schema
How do I perform a systematic code review on a feature diff?▼

A systematic code review evaluates a feature diff for correctness, maintainability, and fitness for purpose. It examines structure, naming, complexity, coupling, and test gaps, then grades findings by severity to prioritize fixes.

How does a severity model help prioritize code review findings?▼

A severity model prioritizes code review findings by grading each issue into Blocking, Recommendation, or Observation tiers. This ensures the highest-impact defects are addressed first before moving to minor structural or naming improvements.

What is the best way to detect dead code and complexity smells during a refactor?▼

To detect dead code and complexity smells during a refactor, use a smell-driven inspection approach. This targets bloaters, change preventers, couplers, and dispensables to systematically uncover maintainability issues across the diff.

Can static analysis cover test and documentation gaps in a code change?▼

Yes, static analysis can cover test and documentation gaps in a code change. The review process specifically inspects missing test coverage and documentation alongside structural complexity and coupling issues to assess fitness for purpose.

Does this code review approach evaluate SOLID or GRASP design principles?▼

This code review approach focuses on review mechanics like complexity and coupling rather than evaluating SOLID or GRASP design principles. It points to companion guidance for deeper design-signal analysis to avoid overlapping scopes.

Related Skills

Explore More Software Engineering Skills→
petekppetekp

review

Audit existing code, diffs, PRs, and plans without generating changes.

Community
Intermediate
wesleyegbertowesleyegberto
3

software-design-principles

Apply SOLID, GRASP, and modularisation principles during code reviews.

Community
Advanced
amano--amano--

semgrep

Analyze code for bugs, standards, and security vulnerabilities across languages.

Community
Intermediate
alicangnllalicangnll

Code Quality Metrics

Analyze binary code for maintainability and security issues.

Community
Advanced