code-smells

Identify refactoring-relevant code smells in pull request diffs.

Updated May 15, 2026

Search Tags:#code review #refactoring #maintainability #quality gate #code smells #evidence-based #PR diff

Ready to run

npx skills add https://github.com/mattnowdev/super-review --skill code-smells-mattnowdev

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you find maintainability problems in PRs by translating common refactoring/code-smell patterns into actionable review guidance, while avoiding noisy “maybe” feedback.

Core Features & Use Cases

Refactoring.guru / Fowler-style smell coverage: Detects bloaters, OO abusers, change preventers, dispensables, and couplers tailored to PR contexts.
PR-diff scoped triggering: Loads automatically on signals like large single-file changes, new classes with many methods, cross-file function moves, or when explicitly requested.
Evidence-focused calibration: Treats smells as suggestions and flags them only when they are load-bearing (cause pain, block near-future change, or increase cost with the current diff).

Quick Start

Ask for a refactor/code-smell review of a changed module with a large diff by invoking the skill for the PR.

Frequently Asked Questions about code-smells

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

FAQPage Schema

How do I find code smells in a pull request diff?▼

To find code smells in a pull request diff, this skill applies a Fowler-style catalog to detect bloaters, OO abusers, and couplers. It scopes triggers to large single-file changes and cross-file function moves to provide evidence-grounded suggestions.

What is a refactoring code smell and how does it affect maintainability?▼

A refactoring code smell is a maintainability problem like a bloater or change preventer that blocks near-future changes. This skill identifies load-bearing smells in PRs to recommend concrete refactor directions and avoid noisy feedback.

How do I review a large single-file change for refactoring issues?▼

Reviewing a large single-file change for refactoring issues involves triggering this skill on the PR diff. It evaluates changes against a Refactoring.guru catalog to flag load-bearing smells and recommend concrete refactor directions.

Does this code review skill flag all potential code smells in a PR?▼

No, this code review skill does not flag all potential smells. It uses evidence-focused calibration to flag only load-bearing smells that cause pain or increase cost with the current diff, avoiding generic noisy feedback.

Can I use this skill for quality gate checks on new classes with many methods?▼

Yes, you can use this skill for quality gate checks on new classes with many methods. It triggers automatically on this scenario and applies an OO abuser detection catalog to produce calibrated, evidence-grounded suggestions.