Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From codescene
Generates quantified business justifications for refactoring work, translating code health metrics into delivery speed and defect reduction arguments for stakeholders.
npx claudepluginhub codescene-oss/codescene-mcp-server --plugin codesceneHow this skill is triggered — by the user, by Claude, or both
Slash command
/codescene:making-the-business-case-for-code-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the user needs quantified justification for refactoring work. The purpose is to convert current Code Health into a clear argument about delivery speed and defect reduction.
Explains Code Health fundamentals, score interpretation, and why it matters for maintainability and delivery speed.
Assesses tech debt by identifying, classifying, and prioritizing maintainability problems to build a refactoring roadmap. Draws on twelve classic engineering books.
Analyzes codebase complexity, dependencies, dead code, tech debt, and git hotspots. Produces a health score and rescue plan for legacy projects or external repo evaluation.
Share bugs, ideas, or general feedback.
Use this skill when the user needs quantified justification for refactoring work. The purpose is to convert current Code Health into a clear argument about delivery speed and defect reduction.
Do not use this skill to explain Code Health fundamentals. Use explaining-code-health for that.
code_health_refactoring_business_case: Generate modeled outcomes for one file.code_health_score: Optional supporting baseline when the user wants the current score called out separately.code_health_refactoring_business_case for the target file.code_health_score or code_health_review to show why the file is a refactoring candidate.