mcaf-solid-maintainability
/mcaf-solid-maintainability
Refactor coupled or oversized code by responsibility, apply repository maintainability limits, and document justified exceptions. Use for design quality changes or maintainability policy.
- Author
- managedcode ↗
- Repository
- MCAF ↗
- Licence
- CC-BY-4.0
- Last repository change
- 11.10.2026
Assessment and security
- Files in this package
- 4
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 11.10.2026, without references to retired models or APIs.
CC-BY-4.0, otwarta.
What it does and when to use it
Refactor coupled or oversized code by responsibility, apply repository maintainability limits, and document justified exceptions. Use for design quality changes or maintainability policy.
Original author description
Refactor coupled or oversized code by responsibility, apply repository maintainability limits, and document justified exceptions. Use for design quality changes or maintainability policy.
How it works
- Workflow
- References
SKILL.md preview
--- name: mcaf-solid-maintainability description: "Refactor coupled or oversized code by responsibility, apply repository maintainability limits, and document justified exceptions. Use for design quality changes or maintainability policy." metadata: compatibility: "Requires repository write access; uses maintainability limits from root or local `AGENTS.md`." --- # MCAF: SOLID Maintainability Read root/local `AGENTS.md`, the complete affected behavior, callers, contracts, and tests. Preserve accepted architecture and observable behavior during a local refactor; seek approval for material boundary changes. ## Workflow 1. Read the active `file_max_loc`, `type_max_loc`, `function_max_loc`, `max_nesting_depth`, and `exception_policy` from governance. Numeric limits belong there, never in skill metadata. 2. Split by responsibility and cohesion, with explicit dependencies and composition where appropriate. Line count identifies a smell; moving lines alone does not fix it. 3. Apply the repo's literal/configuration rules. Give behavior-defining values a named owner rather than scattering duplicated literals. 4. Complete every affected call site, integration, and regression test. Review behavior preservation, failure paths, and test quality before formatting and planned verification. 5. When a temporary limit breach is justified, document its reason, exact scope, owner, and removal plan where `exception_policy` requires. A debt record does not complete unfinished in-scope work. Deliver a cohesive implementation or the requested policy update, with evidence that behavior and required gates remain sound. ## References - For policy keys and temporary breaches: [limits and exceptions](references/limits-and-exceptions.md). - For design signals: [maintainability](references/maintainability.md). - For runtime failures and API error handling: [exception handling](references/exception-handling.md).
Files in this package (4)
- SKILL.md 2 KB
- references/exception-handling.md 1 KB
- references/limits-and-exceptions.md 1 KB
- references/maintainability.md 1 KB
Versions
The database has no other skills named mcaf-solid-maintainability.
Database snapshot: 13.11.2026 · package version 37c212c2a5be (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100code-refactoring-refactor-clean
Refactor code with clean code principles, SOLID design patterns, and modern software engineering practices to improve quality, maintainability, and performance. Use when cleaning up or restructuring existing code. - 100codebase-cleanup-refactor-clean
Refactor code with clean code principles, SOLID design patterns, and modern software engineering practices to improve quality, maintainability, and performance. Use when cleaning up or restructuring existing code. - 90mcaf
Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules. USE FOR: creating or tightening root and local AGENTS.md policy; placing durable engineering context; defining the repository's own verification contract. DO NOT… - 100code-review-assistant
Analyzes code changes for security vulnerabilities, performance issues, and maintainability concerns. Provides structured feedback with SOLID principle checks and anti-pattern detection. Triggers on: "review this code", "code review", "check my PR", "review my changes". - 100v1-deep-review
Use when reviewing a PR or branch for merge risk or maintainability. Triggers on "review this PR", "code review", or "maintainability audit". - 100refactor
Refactor code for quality and maintainability. Use for cleanup and tech debt reduction.