Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From codescene
Explains Code Health fundamentals, score interpretation, and why it matters for maintainability and delivery speed.
npx claudepluginhub codescene-oss/codescene-mcp-server --plugin codesceneHow 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.
Generates quantified business justifications for refactoring work, translating code health metrics into delivery speed and defect reduction arguments for stakeholders.
Scores a project across PR quality, architecture, tech debt, and test quality in a single pass, drawing on twelve classic engineering books. Useful for big-picture codebase health assessments before releases or when onboarding a team.
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 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.