qual-refactoring-priority
Domain: qual · Model class: cheap
Description
Section titled “Description”Use this skill when the user wants to work on Ranking and prioritizing code refactoring work using churn, coupling, and business impact signals. Triggers include “prioritize refactoring”, “what should I refactor first”, “technical debt ranking”. Do NOT use when analyze code quality in detail (use core-code-analysis).
Purpose
Section titled “Purpose”Ranking and prioritizing code refactoring work using churn, coupling, and business impact signals. This skill provides structured guidance, references, and worked examples to help produce high-quality, actionable outputs.
Trigger Phrases
Section titled “Trigger Phrases”- “prioritize refactoring”
- “what should I refactor first”
- “technical debt ranking”
- “hotspot analysis for refactoring”
- “code debt core-prioritization”
Anti-Triggers
Section titled “Anti-Triggers”- analyze code quality in detail (use core-code-analysis)
- design a refactoring strategy (use core-system-design)
Intake Questions
Section titled “Intake Questions”- What is the user’s goal and current state?
- What constraints (time, team, compliance) apply?
- Are there existing artifacts (specs, code, benchmarks) to reference?
Output Contract
Section titled “Output Contract”- quality findings
- evidence-grounded issues
- prioritized fixes
- verification guidance