skills.rest
Burburton
BurburtonCOMMUNITY
Explore all skills by this author →
GitHub

maintainability-review

Analyze code changes and produce a structured maintainability review report.

Updated Mar 22, 2026
Search Tags:#documentation#maintainability#dependencies#complexity#code-review#technical-debt#solid-principles
One-click install
npx skills add https://github.com/Burburton/amazing-specialists --skill maintainability-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: maintainability-review
Source: https://github.com/Burburton/amazing-specialists/tree/main/templates/pack/full/.opencode/skills/reviewer/maintainability-review
Command: npx skills add https://github.com/Burburton/amazing-specialists --skill maintainability-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The maintainability-review skill helps teams identify long-term maintainability issues in code reviews, enabling proactive refactoring decisions.

Core Features & Use Cases

  • Independent verification of maintainability claims vs reviewer analysis
  • Complexity, SOLID, and dependency analysis with actionable recommendations
  • Documentation and test coverage assessment to surface gaps and debt

Quick Start

Run the maintainability-review skill on a changed module to generate a formal review report.

Frequently Asked Questions about maintainability-review

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

FAQPage Schema
How do I assess code maintainability risks in a large pull request?▼

To assess code maintainability in a large pull request, run the maintainability-review skill on the changed module to generate a structured report analyzing complexity, SOLID compliance, dependencies, and technical debt.

What is the best way to identify technical debt during a legacy refactor?▼

Identifying technical debt during a legacy refactor requires systematically analyzing code complexity, dependency coupling, and documentation gaps. The maintainability-review process produces a formal report with severity classifications to guide proactive refactoring decisions.

How does code review check SOLID principles and dependency complexity?▼

Code review checks SOLID principles and dependency complexity by independently verifying maintainability claims against the actual code changes, analyzing architectural coupling, and disclosing severity-classified risks in a structured YAML output report.

Can I use a structured report to audit architecture and documentation gaps?▼

Yes, you can audit architecture and documentation gaps by generating a maintainability-review report that assesses test coverage, documentation status, and structural complexity, enforcing independent verification to surface hidden debt.

When should I not use an automated maintainability review for refactoring?▼

You should avoid relying solely on an automated maintainability review when dealing with highly dynamic runtime dependencies or business logic requiring domain-specific context, as the analysis focuses on structural complexity, SOLID compliance, and static technical debt.

Related Skills

Explore More Software Engineering Skills→
kapilvirenahujakapilvirenahuja
3

build-dependency-graph

Build module-level dependency graphs with cycle and hub detection.

Community
Intermediate
cslsoftwarescslsoftwares

quality-tech-debt-tracker

Register, classify, and prioritize technical debt with maintenance costs and remediation paths.

Community
Advanced
Ramprasad4121Ramprasad4121
1

audit-prep-assistant

Prepare codebases for security review with static analysis and documentation.

Community
Advanced
takemo101takemo101

code-quality-rules

Define and enforce code quality rules for file size, architecture, SOLID, naming, and testing.

Community
Advanced