skills.rest
xbpk3t
xbpk3tCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

maintainability-reviewer

Detect premature abstractions, dead code, coupling, and unclear naming in source code.

Updated Aug 27, 2026
Search Tags:#code review#maintainability#abstraction#dead code#coupling#naming#indirection
One-click install
npx skills add https://github.com/xbpk3t/ce-codex --skill maintainability-reviewer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintainability-reviewer
Source: https://github.com/xbpk3t/ce-codex/tree/main/skills/maintainability-reviewer
Command: npx skills add https://github.com/xbpk3t/ce-codex --skill maintainability-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill finds structural code issues that increase future maintenance cost by identifying premature abstractions, unnecessary indirection, dead code, harmful coupling, and names that obscure intent.

Core Features & Use Cases

  • Structural detection: Flags abstractions with a single implementation, factories or interfaces without consumers, and layers of indirection that add cognitive cost.
  • Dead code and coupling analysis: Identifies commented-out code, unused exports, unreachable branches, circular dependencies, and modules that improperly share mutable state.
  • Naming and intent clarity: Highlights identifiers and APIs whose names fail to convey purpose, and suggests clearer alternatives.
  • Use Case: During a pull request review, use this Skill to produce an evidence-backed list of maintainability issues with confidence levels and concrete refactor suggestions.

Quick Start

Ask the maintainability-reviewer to review the attached codebase and list maintainability issues with confidence scores and actionable recommendations.

Frequently Asked Questions about maintainability-reviewer

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

FAQPage Schema
How do I identify premature abstractions and dead code during a code review?▼

To find unnecessary indirection and harmful coupling, analyze call relationships and shared mutable state across modules. This structural audit identifies factories without consumers, circular dependencies, and layers adding cognitive cost, providing evidence-backed refactor candidates.

How to review a pull request for maintainability issues with confidence scores?▼

Reviewing a pull request for maintainability involves scanning implementations, unused symbols, and naming patterns to produce an evidence-backed list of structural issues. The output provides confidence levels and actionable recommendations for each refactor candidate.

Can I use an automated maintainability audit across modules and libraries?▼

Yes, maintainability auditing applies across modules and libraries by detecting dead code, premature abstractions, and harmful coupling. It analyzes structural implementations and unused symbols to flag concrete refactor candidates during architectural reviews.

Why does harmful coupling and unnecessary indirection increase future maintenance cost?▼

Harmful coupling and unnecessary indirection increase maintenance cost by adding cognitive load and obscuring intent. Identifying single-implementation abstractions, circular dependencies, and unclear naming through structural analysis provides evidence-based findings to reduce this cost.

Related Skills

Explore More Software Engineering Skills→
C0ntr0lledCha0sC0ntr0lledCha0s
8

module-health

Assess Logseq template module health and generate refactoring recommendations.

Community
Basic
TakfesTakfes

python-simplifier

Analyze Python code for maintainability issues and refactoring opportunities.

Community
Advanced
rsmdtrsmdt
381

specification-compliance

Validate implementations against documented specifications with structured compliance reporting.

Community
Advanced
archibatearchibate
6

code-quality-metrics

Measure code complexity and quality metrics across multi-language repositories.

Community
Intermediate