health

Aggregate type safety, lint, tests, and dead-code signals into a 0-10 code health score.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/singhianand23045/GarryTan --skill health-singhianand23045
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/singhianand23045/GarryTan/tree/main/health
Command: npx skills add https://github.com/singhianand23045/GarryTan --skill health-singhianand23045

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality is not a single metric. This Skill collects type safety, lint cleanliness, test coverage, and dead-code signals, and surfaces a weighted 0-10 health score with trends over time.

Core Features & Use Cases

  • Central health score: combines type checks, lint results, tests, and dead-code detection into a single, trackable metric.
  • Trend analysis: shows health trajectories to spot regressions and rate improvements.
  • Use Case: a team can monitor code health across repositories and branches to prioritize refactors that improve reliability and maintainability.

Quick Start

Run the health skill to generate a live code-quality dashboard for your repository.

Frequently Asked Questions about health

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

FAQPage Schema
How do I calculate a code health score for my repository?

Code health is quantified by combining type safety, lint cleanliness, test coverage, and dead-code signals into a weighted 0-10 score. You need to run a type checker, linter, test runner, and dead-code detector to generate the metric.

What is code health monitoring and how does it track regressions?

Code health monitoring tracks quality trends over time by aggregating type checks, lint results, tests, and dead-code detection. Trend analysis surfaces trajectories to spot regressions and rate improvements across per-repo and per-branch views.

Can I track code quality across multiple repositories and branches?

Yes, you can track code quality across multiple repositories and branches. The Skill provides per-repo and per-branch views to monitor health over time and flag drift in ongoing software projects of any size.

What's the best way to combine lint, test coverage, and dead-code detection into one metric?

The best way to combine these signals is using a weighted 0-10 health score that aggregates type safety, lint cleanliness, test coverage, and dead-code detection. This creates a single, trackable metric with trend analysis.

Do I need to run a type checker and linter before calculating code health?

Yes, you need to run a type checker, linter, test runner, and dead-code detector before calculating code health. The Skill aggregates the outputs from these four tools to compute the final weighted 0-10 score.

Why does my code health score drop even when test coverage increases?

Your code health score may drop when test coverage increases if other weighted signals decline. The score combines type safety, lint cleanliness, tests, and dead-code detection, so regressions in type checking or increased dead-code can offset coverage gains.