Skip to content
Skills Library
Programming · Learning & explanation

explaining-code-health

/explaining-code-health

Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.

Licence
Apache-2.0
Last repository change
27.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.

Original author description

Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.

How it works

  1. Overview
  2. When to Use
  3. Quick Reference
  4. Implementation
  5. Common Mistakes
Original SKILL.md headings · 32 lines, 199 words
SKILL.md preview
---
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.
---

# Explaining Code Health

## Overview

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.

## When to Use

- A user asks what Code Health is.
- A user asks how to interpret scores or what a better score implies.
- A stakeholder needs a concise explanation of why Code Health matters.

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.

## Quick Reference

- `explain_code_health`: Fundamentals of the Code Health model.
- `explain_code_health_productivity`: Evidence and framing around speed, quality, and productivity.

## Implementation

1. Use `explain_code_health` for fundamentals.
2. Use `explain_code_health_productivity` when the user also wants delivery or defect framing.
3. Tailor the explanation to the current task, repository, or planning decision.
4. Keep the explanation concrete and connect it to maintainability outcomes.

## Common Mistakes

- Using abstract language without connecting it to everyday engineering decisions.
- Jumping to ROI claims when the user only asked for fundamentals.
- Repeating documentation verbatim instead of tailoring it to the user’s context.

Versions

The database has no other skills named explaining-code-health.

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version c766cfae5204 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100audit
    Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
  • 100project-health-auditor
    Comprehensive codebase health analysis. Use when reviewing code quality, identifying technical debt, checking dependencies, or assessing project structure.
  • 90st-explain
    Explain how a piece of code works, why it is built that way, and what that means, in plain language a person can follow. Use for 'how does X work', 'why is it like this', 'teach me this', onboarding to a subsystem, or /st-explain.
  • 100phx-audit
    Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
  • 90ai-workflow
    This skill should be used when explaining why Bee follows spec-first TDD workflows, or when teaching mode is on. Contains the reasoning behind spec → plan → test → code ordering.
  • 90guiding-refactoring-with-code-health
    Use when refactoring unhealthy code and needing Code Health findings to choose small safe steps and verify improvement.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.