health

Aggregate type checks, linting, tests, and dead-code detection into a health metric.

1|Updated May 27, 2026
One-click install
npx skills add https://github.com/mi179/claude-skills --skill health-mi179
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/mi179/claude-skills/tree/main/user/gstack/health
Command: npx skills add https://github.com/mi179/claude-skills --skill health-mi179

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code health assessment by aggregating signals from multiple tooling into a single, comparable quality score, enabling teams to spot deterioration early.

Core Features & Use Cases

  • Integrates type checkers, linters, test runners, dead code detectors, and shell linters to produce a unified health metric.
  • Tracks health trends over time and surfaces actionable insights for CI, PR reviews, and codebase improvements.
  • Use Case: run health checks on large repositories to quantify code quality and guide refactoring priorities.

Quick Start

Run the health check to generate the current codebase health score and a trend report.

Frequently Asked Questions about health

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

FAQPage Schema
How do I aggregate code quality signals into a single health score?

Code health scores are generated by aggregating deterministic checks from type checkers, linters, test runners, and dead code detectors into a unified metric. This enables teams to quantify codebase quality and spot deterioration early.

How does tracking code health trends over time work in CI pipelines?

Tracking code health trends works by running deterministic checks in CI pipelines and storing timestamped data. This provides long-term visibility into code quality, enabling teams to plan refactoring improvements based on historical metrics.

Can I use code quality metrics to guide refactoring priorities for large repositories?

Code quality metrics can guide refactoring priorities by surfacing actionable insights from dead-code detection, shell linting, and test results. Running health checks on large repositories quantifies exactly where structural improvements are needed.

What is a code health dashboard and when do I need it for PR reviews?

A code health dashboard aggregates type checks, linting, and test failures into a comparable quality score. You need it during PR reviews to measure codebase health objectively and prevent quality deterioration before merging changes.

Does this code health metric work for local development environments?

The code health metric works across both local development environments and CI pipelines. It runs deterministic checks locally to provide immediate feedback on code quality before pushing changes, ensuring consistent health scoring.

What's the best way to measure codebase health using static analysis and linting?

The best way to measure codebase health is combining static analysis, linting, and test execution into a single comparable score. Aggregating these deterministic signals provides a comprehensive view of code quality and tracks trends over time.