Menu
Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when refactoring unhealthy code and needing Code Health findings to choose small safe steps and verify improvement.
Use when a user asks for ROI, stakeholder justification, delivery impact, or defect-risk reduction from improving Code Health in a file.
Use when AI-generated or AI-modified changes need a Code Health gate before commit, handoff, or pull request.
Run linting and unit tests against the current repository, auto-discovering the correct commands from Justfile, Makefile, pyproject.toml, or package.json.
Create a conventional commit from staged changes, with a diff-derived description body.
Reliably obtain a non-empty unified git diff for the current branch using safe fallbacks (origin/HEAD...HEAD, origin/main...HEAD, origin/master...HEAD) and return structured JSON containing the diff and the command used.
| name | explaining-code-health |
| description | Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development. |
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.