health

Aggregate code-quality tool results into a health score and trend data.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

A code quality dashboard that aggregates the results of your project's tools (type checker, linter, test runner, dead code detector, and shell linter) into a single, actionable health score and trend history.

Core Features & Use Cases

  • Composite health scoring: wraps multiple project tools to produce a 0-10 score and track health trends over time.
  • Deterministic health checks: runs a defined set of checks to provide repeatable results for CI or local development.
  • Use Case: when you need a quick, objective view of code health across commits and branches.

Quick Start

Run the health dashboard to generate the latest health report for the project.

Frequently Asked Questions about health

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

FAQPage Schema
What is a code quality dashboard and how does it track code health?

A code quality dashboard aggregates telemetry from type checkers, linters, and test runners to produce a single 0-10 code health score. It tracks this health trend over time across commits to provide an objective view of project stability.

How do I aggregate linter and test runner results into a single health score?

You aggregate linter and test runner results by running a health dashboard that wraps multiple project tools. It deterministically combines these code-quality signals into a unified score and trend history for quick assessment.

Can I use this code health dashboard for regular CI health checks?

Yes, you can use this code health dashboard for regular CI health checks. It runs a defined set of deterministic checks across type checkers and dead code detectors to provide repeatable results suitable for continuous integration.

Does the code quality dashboard work with type checkers and dead code detectors?

The code quality dashboard works directly with type checkers, linters, test runners, dead code detectors, and shell linters. It satisfies integration with these tools to aggregate their individual results into a composite health score.

What's the best way to monitor code health progress over time across commits?

The best way to monitor code health progress over time is to use a dashboard that records deterministic health checks. It generates a historical trend data set by tracking the composite 0-10 score across multiple project commits and branches.

Are there limitations to using a single composite score for code quality assessment?

A single composite score for code quality assessment aggregates multiple tool outputs into a 0-10 rating, which may obscure specific individual tool failures. Review the underlying type checker and linter telemetry if you need granular diagnostic details.