code-review

Identify correctness, design, and maintainability issues in code changes.

1|Updated Apr 2, 2026

Search Tags:#testing #architecture #maintainability #quality #code-review #pull-request #diff-analysis

Ready to run

npx skills add https://github.com/thomassloboda/ai-stuff --skill code-review-thomassloboda

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps reviewers quickly surface correctness gaps, design flaws, and maintainability risks in code changes, enabling faster, higher-quality merges.

Core Features & Use Cases

Structured evaluation of diffs and pull requests for correctness, architecture, testing, and maintainability.
Guided review criteria covering regression risks, naming quality, and potential architecture violations.
Quality signals with Sonar-style concerns when applicable to drive focused improvements.

Quick Start

Review the latest diff or pull request to surface correctness, design, and maintainability issues.

Frequently Asked Questions about code-review

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

FAQPage Schema

How do I identify high-signal issues in a pull request?▼

Identifying high-signal issues in a pull request involves evaluating the diff for correctness gaps, regression risks, architecture violations, and test coverage. This structured evaluation surfaces design flaws and maintainability risks to enable faster merges.

What is the best way to review a heavy refactor for maintainability?▼

Reviewing a heavy refactor for maintainability requires checking naming quality and applying Sonar-style quality concerns. This evaluates the changes against design rules to ensure the code structure remains robust and easy to maintain.

Can I use automated code review to check architecture violations in a diff?▼

You can check architecture violations in a diff using structured code review. It evaluates the changes against architectural rules and regression risks, ensuring the modification does not break existing design constraints.

Does this code review approach evaluate test coverage and regression risk?▼

Yes, this code review approach evaluates test coverage and regression risk. It analyzes the diff to surface testing gaps and correctness issues, ensuring potential regressions are identified before merging the code changes.

When do I need a structured code review for my local diff?▼

You need a structured code review for your local diff when the changes have testing or architectural implications. It evaluates correctness, design, and maintainability to surface high-signal issues before creating a pull request.