maintainability-criteria

Define measurable maintainability criteria for codebases and services.

1|Updated Nov 29, 2025

Search Tags:#refactoring #maintainability #modularity #complexity #code-quality #ci #test-coverage

Ready to run

npx skills add https://github.com/SSiertsema/claude-code-plugins --skill maintainability-criteria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: maintainability-criteria
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/maintainability-criteria/skills/maintainability-criteria
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill maintainability-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define measurable maintainability criteria for a codebase or service to guide quality gates and audits.

Core Features & Use Cases

Establish thresholds for code complexity, test coverage, documentation, modularity, and deprecation playbooks.
Wires into CI checks and review processes to enforce maintainability over time.
Applies across greenfield or legacy codebases with phased drawdown policies.

Quick Start

Define a baseline of maintainability criteria for your codebase and wire them to CI checks for ongoing enforcement.

Frequently Asked Questions about maintainability-criteria

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

FAQPage Schema

How do I define maintainability criteria for a codebase to guide CI quality gates?▼

You can define measurable maintainability criteria by establishing thresholds for code complexity, test coverage, documentation, and modularity, then wiring those thresholds directly into CI checks and review processes for ongoing enforcement.

What measurable code quality thresholds should I set for unit and integration workflows?▼

Measurable code quality thresholds should include complexity caps, test coverage targets, modularity rules, and documentation requirements, specifically tailored to guide unit, integration, and E2E workflows within your CI pipeline.

Can I enforce maintainability thresholds across legacy codebases with existing complexity issues?▼

Yes, you can enforce maintainability thresholds across legacy codebases by applying a phased drawdown policy with legacy tolerance, allowing you to manage existing complexity issues while preventing further degradation over time.

How do I set up a refactoring budget and deprecation playbook for my service?▼

Setting up a refactoring budget involves defining specific maintainability criteria and pairing it with a deprecation playbook, establishing clear policies for dependency management and legacy drawdown to systematically reduce technical debt.

Does this approach to maintainability and modularity work across different architectures?▼

Yes, defining maintainability and modularity rules applies to codebases across different languages and architectures, enabling you to establish consistent quality gates and review processes regardless of your specific technical stack.

What is the best way to introduce maintainability criteria in a greenfield codebase?▼

The best way to introduce maintainability criteria in a greenfield codebase is to establish a baseline of complexity caps, test coverage targets, and modularity rules, then wire them directly into CI checks for phase-based setup and ongoing enforcement.