health

Name: health
Availability: InStock
Author: stayconnectquick

Aggregate code quality metrics into a 0-10 health score with trends.

Updated May 6, 2026

Search Tags:#code-quality #lint #ci #type-check #quality-score #health-dashboard

Ready to run

npx skills add https://github.com/stayconnectquick/gstack --skill health-stayconnectquick

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is codebase", "run all checks", "quality score". (gstack)

Core Features & Use Cases

Wraps type checkers, linters, test runners, dead-code detectors, and shell linters to produce a single health score and trend history.
Provides a health dashboard for CI pipelines and manual reviews.
Use case: monitor the health of a codebase over time to catch quality regressions early.

Quick Start

Run the health skill to generate the latest health report 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 quantify codebase health into a single quality score?▼

Track codebase health over time by computing a weighted composite 0-10 quality score from linters, type checkers, and test runners. This score is logged historically to identify quality trends and catch regressions early.

What is the best way to track code quality trends in a CI pipeline?▼

Code quality trends in a CI pipeline are tracked by running a health check that aggregates quality metrics into a historical dashboard. This monitors the codebase over time to catch regressions during continuous integration.

Can I use existing linters and type checkers to generate a code quality dashboard?▼

Yes, existing linters, type checkers, test runners, and dead code detectors are wrapped to generate a code quality dashboard. The skill integrates these tools to produce a unified health score without replacing them.

Does the code quality score work across multiple programming languages?▼

Yes, the code quality scoring works across languages by integrating with various type checkers and linters. It aggregates results from whatever project tools are already configured in the repository.

Why do I need a composite health score instead of just running linters separately?▼

A composite health score standardizes results from separate linters, type checkers, and dead code detectors into a single 0-10 value. This simplifies monitoring and provides historical trend tracking across the entire codebase.

When should I run a codebase health check in my development workflow?▼

A codebase health check should be run in CI pipelines or during manual reviews to monitor quality regressions early. Running it continuously generates trend history that highlights when code quality starts degrading.