health

Runs project linters, type checkers, and test suites to compute a weighted 0-10 code quality score.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/Simon-YHKim/eject-button --skill health-simon-yhkim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/Simon-YHKim/eject-button/tree/main/.claude/skills/health
Command: npx skills add https://github.com/Simon-YHKim/eject-button --skill health-simon-yhkim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Code quality is spread across many tools — type checkers, linters, test runners, dead code detectors — and no single number tells you if the codebase is getting better or worse. This Skill runs every available check, scores each category, and produces one composite dashboard with trend tracking over time. ## Core Features & Use Cases - Tool auto-detection: Detects tsc, biome, eslint, ruff, pytest, cargo test, go test, knip, and shellcheck from project config files, or reads a pinned ## Health Stack section from CLAUDE.md. - Weighted composite scoring: Scores type check (25%), lint (20%), tests (30%), dead code (15%), and shell lint (10%) on a 0-10 scale and combines them into one composite score. - Trend tracking and regression analysis: Appends each run to a JSONL history file, compares against the last 10 runs, and highlights which categories declined with the exact errors responsible. - Use Case: After a week of feature work, run the health check to see the composite score dropped from 9.4 to 8.2 because 12 new lint warnings and 2 failing tests were introduced, then get a prioritized fix list ranked by category weight. ## Quick Start Ask the assistant to run a health check on this codebase and show the quality dashboard with trend data.

Frequently Asked Questions about health

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check overall code quality across multiple tools?

Run the health check, which auto-detects your type checker, linter, test runner, dead code detector, and shell linter, then runs each one and combines the results into a weighted 0-10 composite score with a dashboard.

How is the code health score calculated?

Each category is scored 0-10: type check weighs 25%, lint 20%, tests 30%, dead code 15%, and shell lint 10%. The composite is the weighted sum, and skipped tools have their weight redistributed proportionally.

Can I pin which tools the health check runs?

Yes. Add a `## Health Stack` section to CLAUDE.md listing exact commands for typecheck, lint, test, deadcode, and shell. The skill reads that section first and skips auto-detection entirely.

Does the health check fix the issues it finds?

No. It is strictly read-only by design. It presents the dashboard, raw tool output for failures, and prioritized recommendations, but never modifies code. You decide what to act on.

How do I track code quality trends over time?

Each run appends a JSONL entry with per-category scores to a project history file. On subsequent runs the skill shows the last 10 entries, the score delta, and which specific categories regressed with the errors responsible.

What happens if a tool like knip or shellcheck is not installed?

Missing tools are recorded as SKIPPED, not failures. Their weight is redistributed proportionally among the remaining categories so the composite score stays fair.