health

Name: health
Availability: InStock
Author: prestonigo

Run type checker, linter, test runner, dead code detector, and shell linter to compute a weighted 0-10 health score.

Updated Aug 23, 2026

Search Tags:#dashboard #code-quality #lint #tests #type-check #trend-analysis

Ready to run

npx skills add https://github.com/Prestonigo/Claude-Skills --skill health-prestonigo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: health
Source: https://github.com/Prestonigo/Claude-Skills/tree/main/gstack-main/health
Command: npx skills add https://github.com/Prestonigo/Claude-Skills --skill health-prestonigo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregate and score code health by running a suite of tooling (type checker, linter, test runner, dead code detector, and shell linter) and combining results into a weighted 0-10 health score. It tracks trends over time to show improvement or degradation and supports routine health checks and quality-score reviews.

Core Features & Use Cases

Consolidates multiple quality tools into a single, interpretable health score (0-10) with weighting.
Tracks health trends over time to visualize improvements or regressions.
Used to assess code quality, plan refactors, and schedule comprehensive health checks.

Quick Start

Run a full health check to compute the 0-10 health score and review trend history.

Frequently Asked Questions about health

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

FAQPage Schema

How do I calculate a single code quality score from linters, type checkers, and tests?▼

You can track code health trends by computing the weighted 0-10 health score over time, which visualizes improvements or regressions across your codebase. The dashboard-like summary stores historical health-score data for routine quality reviews.

What's the best way to consolidate dead code detection and shell linting into a routine health check?▼

The best way to consolidate dead code detection and shell linting into a health check is running a full suite scan that aggregates results into a weighted 0-10 score. This approach supports routine checks and refactor planning for any codebase size.

Does the code health dashboard work with codebases of any size?▼

Yes, the code health dashboard works with codebases of any size to assess overall quality and track trends. It requires the underlying tools, such as the type checker and linter, to be available in the environment to produce the summary.

Do I need to install specific dependencies before running a code health check?▼

You need the underlying tools, including the type checker, linter, test runner, dead code detector, and shell linter, to be available before running a code health check. The Skill requires these external dependencies to execute and generate the weighted score.

Why does my weighted health score change between different codebase scans?▼

Your weighted health score changes because the tool tracks trends over time by re-running type checkers, linters, and tests, reflecting current code quality. This historical trend analysis visualizes recent improvements or regressions in the codebase.