القائمة
Use when a user asks for ROI, stakeholder justification, delivery impact, or defect-risk reduction from improving Code Health in a file.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | making-the-business-case-for-code-health |
| description | Use when a user asks for ROI, stakeholder justification, delivery impact, or defect-risk reduction from improving Code Health in a file. |
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.Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.
Use when refactoring unhealthy code and needing Code Health findings to choose small safe steps and verify improvement.
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.