health

Aggregate type checking, linting, tests, dead code detection, and shell hygiene into a health score.

Updated Apr 13, 2026

Search Tags:#dashboard #code-quality #lint #tests #dead-code #type-check #shell-lint

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates type checking, linting, tests, dead code detection, and shell hygiene into a single, trackable health score.

Core Features & Use Cases

Wraps existing project tools to compute a weighted 0-10 health score and track health over time.
Provides a dashboard for CI gates and ongoing quality improvements, surfacing trends and actionable insights.
Use case: run health checks after a large refactor to verify no regressions and to guide where to focus fixes.

Quick Start

Run the health skill to generate a live codebase health dashboard and trend analysis.

Frequently Asked Questions about health

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

FAQPage Schema

How do I aggregate type checking, linting, and test results into a single code health score?▼

Code health is aggregated by wrapping existing project tools like tsc, biome, and bun to compute a weighted 0-10 score. This tracks type checking, linting, tests, dead code, and shell hygiene into one unified metric for your codebase.

What is the best way to track codebase health trends across CI pipelines over time?▼

Tracking codebase health trends is done by storing per-commit health data across CI pipelines. This surfaces regressions and long-term visibility by aggregating type checking, linting, tests, dead code detection, and shell hygiene into a trackable score.

How do I verify code quality and check for regressions after a large refactor?▼

To verify code quality after a refactor, run a health check to generate a live dashboard and trend analysis. This surfaces actionable insights by comparing aggregated type checking, linting, test, and dead code detection results against previous commits.

Does this code health dashboard work with varying languages and core tooling like shellcheck and knip?▼

Yes, the code health dashboard works across codebases of varying languages by depending on core tooling. It integrates shellcheck for shell hygiene and knip for dead code detection alongside tsc, biome, and bun to compute the overall score.

Can I use CI gates to block deployments based on linting and dead code detection metrics?▼

Yes, you can use the generated health dashboard for CI gates by setting thresholds for the weighted 0-10 score. It aggregates linting, dead code detection, and type checking metrics to block deployments when regressions are identified.

Why does my code health score drop after adding new linting and type check rules?▼

A code health score drops because the weighted calculation directly incorporates new linting and type check rule failures. The dashboard surfaces these specific regressions and actionable insights, guiding you to focus fixes where the underlying tools report new issues.