maintainability-review

Review code for maintainability smells and propose behavior-preserving refactor moves.

Updated May 24, 2026
One-click install
npx skills add https://github.com/MWest2020/skill-forge --skill maintainability-review-mwest2020
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintainability-review
Source: https://github.com/MWest2020/skill-forge/tree/main/skills/maintainability-review
Command: npx skills add https://github.com/MWest2020/skill-forge --skill maintainability-review-mwest2020

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Standard code reviews focus on correctness and security, but miss the issues that make future changes expensive: unclear names, long functions, hidden coupling, duplicated logic, and change-amplification. This Skill fills that gap by auditing code strictly for maintainability and refactorability. ## Core Features & Use Cases - Smell-Tagged Findings: Every finding is one line with a location, a tag (name, extract, couple, cohesion, dup, seam, amplify), and the specific behavior-preserving refactor move. - Three Review Scopes: Works on the current diff (default), a single named file, or the whole repository as an audit. - Blast-Radius Ranking: Prioritizes change-amplification smells (one logical change forcing edits across many sites) over cosmetic issues. - Use Case: Before merging a large pull request, ask for a maintainability review to surface duplicated logic and hidden coupling, then apply the suggested refactors while behavior stays unchanged. ## Quick Start Ask the assistant to review the current diff for maintainability and list each finding with its smell tag and refactor move.

Frequently Asked Questions about maintainability-review

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

FAQPage Schema
How do I review code for maintainability issues?

Invoke the review on your current diff, a named file, or the whole repo. It returns one-line findings with a location, a smell tag like extract or couple, and the specific behavior-preserving refactor move to apply.

What code smells does a maintainability review detect?

It detects seven smell categories: misleading names, long multi-responsibility functions, cross-boundary coupling, low cohesion, duplicated logic, missing test seams, and change-amplification where one logical change forces edits across many sites.

Does maintainability review fix bugs or security issues?

No. It is strictly behavior-preserving and proposes refactors only. Correctness bugs go to a normal code review, security holes to a security review, and over-engineering concerns to a separate simplification pass.

Can I review a whole repository instead of just a diff?

Yes. The review supports three scopes: the current diff or uncommitted changes (the default), a single named file, or the entire repository as a full maintainability audit.

When should I not use a maintainability-focused review?

Skip it when you need correctness verification, security analysis, or feature changes, since it only lists behavior-preserving refactors and applies nothing unless explicitly asked.