health

Aggregate project tool outputs into a weighted 0-10 health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and centralizes code quality checks to provide a single health score and historical trends, reducing guesswork and drift in code health.

Core Features & Use Cases

  • Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter) to compute a weighted 0-10 health score.
  • Tracks health trends over time and surfaces regressions to guide refactors and CI gates.
  • Use cases include monitoring a codebase after refactors, during CI runs, or across multiple repositories to compare health.

Quick Start

Run the health dashboard to generate the latest health score for your repository and surface key trends.

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 for my repository?

You can calculate a single code health score by running existing project tools like type checkers, linters, and test runners, then aggregating their results into a weighted 0-10 metric. This process centralizes quality checks and tracks regressions over time.

How does a code health dashboard work for tracking codebase quality?

A code health dashboard works by wrapping your existing quality tools to produce a weighted 0-10 health score and historical analytics. It surfaces regressions automatically, reducing guesswork and drift in code health during CI runs or refactors.

Can I aggregate lint and type check results across multiple repositories?

Yes, you can aggregate lint, type check, and test runner results across multiple repositories to compare health. The tool wraps existing project tools to compute weighted scores, allowing you to monitor health trends and guide refactors across different codebases.

What's the best way to track code health trends over time during CI runs?

The best way to track code health trends during CI runs is to wrap your type checkers, linters, and test runners to compute a weighted 0-10 score. This generates historical analytics and a dashboard to surface regressions and guide refactors.

Do I need to install new linters to compute a weighted health score?

No, you do not need to install new linters. The tool computes a weighted 0-10 health score by wrapping your existing project type checkers, lint tools, test runners, dead code detectors, and shell linters already configured in your environment.

What are the limitations of using a single code health score for refactoring?

A single code health score aggregates existing tool outputs into a 0-10 metric, which may obscure specific lint failures or test errors behind the overall number. You should review the underlying dashboard analytics to identify exact codebase regressions.