health

Aggregate type checks, linters, tests, and dead code into a 0-10 health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality is hard to gauge across tools. This Skill collects type checks, linters, test results, dead code detectors, and shell lint checks into a single, portable health score and trend history.

Core Features & Use Cases

  • Aggregates multiple quality signals into a 0-10 health score you can trust.
  • Tracks health trends over time to spot regressions early.
  • Fits into CI pipelines or local development workflows for quick quality checks.

Quick Start

Run the health dashboard on your repository to generate an actionable health report.

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 signals into a single health score?

You can aggregate code quality signals by running a health dashboard that collects type checks, linters, tests, dead code detection, and shell linting into a weighted 0-10 health score.

Can I track code health trends over time in a CI pipeline?

Yes, you can track code health trends over time by integrating the health dashboard into CI pipelines or local development workflows to generate long-run trend data and spot regressions early.

Do I need language-specific linters and test runners to generate a code health dashboard?

Yes, generating the code health dashboard requires language-specific type checkers, linters, test runners, and dead code detectors to be installed so it can aggregate their results into a portable score.

What is the best way to get a quick code health snapshot for my repository?

The best way to get a quick code health snapshot is to run the dashboard on your repository, which produces an actionable report combining dead code detection, type checks, and linting results.

Why use a unified code health score instead of checking linters and tests separately?

A unified code health score solves the problem of gauging quality across disparate tools, providing a single portable metric and trend history instead of manually interpreting isolated linter and test results.