health

Aggregate type checker, linter, test runner, and dead code detector metrics into a weighted 0-10 health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality dashboards help teams quickly assess how healthy a codebase is by aggregating results from multiple quality tools into a single, comparable score.

Core Features & Use Cases

  • Integrates type checkers, linters, test runners, dead code detectors, and shell linters to compute a weighted 0-10 health score.
  • Tracks health trends over time to highlight regressions and improvements.
  • Use cases include pre-release health checks, onboarding new projects, and ongoing quality governance.

Quick Start

Run a health check to generate a 0-10 health score and trend report for the current project.

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 metrics from multiple linters and test runners into one score?

You can aggregate type checkers, linters, test runners, dead code detectors, and shell lint tools results into a weighted 0-10 health score to assess overall codebase quality.

What is a code health score and how does it track code quality trends over time?

A code health score is a weighted 0-10 metric generated by combining outputs from various quality tools, which you can track historically to highlight regressions and improvements in your codebase.

Can I run a code health check for pre-release validation and onboarding new projects?

Yes, running a health check generates a 0-10 score and trend report suitable for pre-release health checks, onboarding new projects, and ongoing quality governance across standard CI pipelines and local setups.

Does the code health dashboard work with standard CI pipelines and local development setups?

The dashboard applies to codebases with standard CI pipelines and local development setups, orchestrating Bash, Read, Write, Edit, Glob, Grep, and AskUserQuestion handlers to aggregate tool metrics.

What's the best way to drill down into specific linter or test runner results within a code health report?

The best way is to use the drill-down by tool feature, which lets you inspect individual contributions from type checkers, linters, test runners, and dead code detectors to your overall health score.

Why do I need dead code detectors and shell lint tools included in a code quality dashboard?

Including dead code detectors and shell lint tools alongside type checkers and test runners ensures the weighted health score reflects a comprehensive view of codebase health rather than just test coverage.