Stats
Actions
Tags
From codescene
Explains Code Health fundamentals, score interpretation, and why it matters for maintainability and delivery speed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/codescene:explaining-code-healthThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Use this skill when the task is educational or explanatory. The goal is to help users understand the meaning of Code Health and why it matters for maintainability, delivery speed, and defect risk.
Use this skill when the task is educational or explanatory. The goal is to help users understand the meaning of Code Health and why it matters for maintainability, delivery speed, and defect risk.
Do not use this skill when the user needs a quantified ROI projection for a specific file. Use making-the-business-case-for-code-health for that.
explain_code_health: Fundamentals of the Code Health model.explain_code_health_productivity: Evidence and framing around speed, quality, and productivity.explain_code_health for fundamentals.explain_code_health_productivity when the user also wants delivery or defect framing.npx claudepluginhub codescene-oss/codescene-mcp-server --plugin codesceneGenerates quantified business justifications for refactoring work, translating code health metrics into delivery speed and defect reduction arguments for stakeholders.
Assesses code health, technical debt, and refactoring priorities in a Repowise-indexed codebase. Reports file-level scores (1-10) based on complexity, cohesion, churn, and coverage biomarkers.
Scans codebase health by identifying hotspots, risky files, and coupling patterns. Prescribes prioritized refactoring actions with ROI-based guidance. Invoke via /Vitals or rely on auto-activation when discussing code quality.