health

Aggregate type checker, linter, test, and dead-code results into a 0-10 score.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/binfen1/my-skills --skill health-binfen1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/binfen1/my-skills/tree/main/claude-code/health
Command: npx skills add https://github.com/binfen1/my-skills --skill health-binfen1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases often drift from agreed quality standards. This skill provides a centralized health dashboard that aggregates type checks, linters, tests, and dead-code detection to present a single, actionable quality score that teams can track over time.

Core Features & Use Cases

  • Aggregates type checker, linter, test results, and dead-code detector outputs into a single 0-10 score.
  • Tracks trends over time and highlights regressions to guide CI improvements.
  • Use Case: during release planning, run the dashboard to identify hotspots and prioritize refactoring.

Quick Start

Run the health skill on your repository to generate the first health dashboard and baseline trends.

Frequently Asked Questions about health

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

FAQPage Schema
How do I aggregate type checker, linter, and test results into a single code quality score?

You can aggregate type checker, linter, test, and dead-code results into a single 0-10 code quality score by running a centralized health dashboard over your repository. This tracks health trends and highlights regressions over time.

What is a code health dashboard and how does it track project quality?

A code health dashboard aggregates type checks, linters, tests, and dead-code detection outputs to present a single actionable quality score. It tracks health trends over time and highlights regressions to guide CI improvements.

How do I monitor code quality trends and compare branches during CI runs?

To monitor code quality trends and compare branches during CI runs, run a health dashboard that computes a 0-10 composite score from type checker and linter outputs. This maintains trends with historical data to enforce standards.

Does the code health dashboard require specific linter or test runner configurations?

The code health dashboard does not require specific linter or test runner configurations. It integrates with existing project tools by aggregating type checker, linter, test, and dead-code detector outputs into a single composite score.

Can I use a composite quality score to prioritize refactoring during release planning?

Yes, you can use the composite quality score to prioritize refactoring during release planning. Running the health dashboard identifies hotspots across type checks, linters, tests, and dead-code to guide targeted improvements.

What's the best way to identify dead-code and quality hotspots across a repository?

The best way to identify dead-code and quality hotspots is running a health dashboard that aggregates type checker, linter, test, and dead-code detector outputs. This generates a baseline dashboard highlighting regressions and areas needing attention.