refactor-maintainability
Skill9 starsChanged 5 months agoMITView on GitHub
Audit and improve maintainability in ableton-mind. Use for complexity, duplication, dead code, dependency boundaries, confusing modules, safe refactor slices and code-quality hardening.
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for maintainability audits and bounded refactor work.
- Distinctive: line 12
Run or inspect complexity and dependency checks when available.
- Distinctive: line 13
Search for duplicated validation, repeated command parsing, oversized functions, stale TODOs and unclear ownership boundaries.
- Distinctive: line 15
Before changing behavior, coordinate with test-coverage-expansion.
- Very specific: line 17
Verify with focused tests plus lint/typecheck/build as needed.
- Distinctive: line 21
Do not rename MCP tools, JSON-RPC methods, recipe formats or public docs paths without an ADR and explicit scope.
- Distinctive: line 22
Do not introduce abstractions unless they remove real duplication or clarify a boundary.
- Distinctive: line 23
Do not mix formatting-only churn with behavior fixes.
- Very specific: line 27
Write _workspace/quality-audit/maintainability-{N}.md with:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Refactor Maintainability
Use this skill for maintainability audits and bounded refactor work.
Workflow
- Run or inspect complexity and dependency checks when available.
- Search for duplicated validation, repeated command parsing, oversized functions, stale TODOs and unclear ownership boundaries.
- Rank refactor candidates by risk, user impact and test coverage.
- Before changing behavior, coordinate with test-coverage-expansion.
- Refactor in small slices that preserve public contracts.
- Verify with focused tests plus lint/typecheck/build as needed.
Refactor Rules
- Do not rename MCP tools, JSON-RPC methods, recipe formats or public docs paths without an ADR and explicit scope.
- Do not introduce abstractions unless they remove real duplication or clarify a boundary.
- Do not mix formatting-only churn with behavior fixes.
Report Format
Write _workspace/quality-audit/maintainability-{N}.md with:
- Candidate.
- Evidence.
- Risk.
- Suggested slice.
- Required tests.
- Verification.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ableton-mind-buildSkill
- ableton-remote-scriptSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- ableton-mind-buildSkill
- ableton-mind-quality-auditSkill
- ableton-remote-scriptSkill
- command-surface-auditSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- local-copilotSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- runtime-release-auditSkill
- security-auditSkill
- test-coverage-expansionSkill
- usability-flow-auditSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.