health

Run code health checks and compute a weighted 0-10 score.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/uzumaki-inc/uzustack --skill health-uzumaki-inc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/uzumaki-inc/uzustack/tree/main/_upstream/gstack/health
Command: npx skills add https://github.com/uzumaki-inc/uzustack --skill health-uzumaki-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality often drifts as projects evolve, making it hard to know when to fix issues. This skill provides a centralized health dashboard by wrapping existing project tools (type checker, linter, test runner, dead code detector, and shell linter) and computing a weighted 0-10 score, enabling trends to be tracked over time and issues surfaced early.

Core Features & Use Cases

  • Wraps type checker, linter, test runner, dead code detector, and shell linter to compute a single health score and visualize trends over time.
  • Provides quick visibility into codebase health, helping teams prioritize fixes before they impact users.
  • Use cases include CI health checks, pre-merge quality gates, and ongoing maintenance dashboards for long-running projects.

Quick Start

Run the health check workflow to generate and view the code quality dashboard 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 track code quality trends over time in a CI pipeline?▼

Code quality health monitoring works by wrapping your existing type checker, linter, test runner, dead code detector, and shell linter to compute a single weighted 0-10 score. This centralized dashboard approach surfaces regressions early and tracks quality trends over time.

What is the best way to set up a pre-merge quality gate for codebase health?▼

Setting up a pre-merge quality gate involves wrapping your type checker, linter, test runner, dead code detector, and shell linter to calculate a weighted health score. This generates a quality gate that prevents regressions from being merged into the codebase.

How does the health score mechanism work for monitoring codebase health?▼

The health score mechanism works by applying weighted checks across your type checker, linter, test runner, dead code detector, and shell linter to compute a 0-10 score. This aggregated score provides quick visibility into codebase health and guides improvements.

Can I use a code quality dashboard for long-running maintenance projects?▼

Yes, a code quality dashboard can be used for long-running maintenance projects to provide ongoing visibility into codebase health. It computes a weighted score from your test runner and linter to help teams prioritize fixes as the project evolves.

What tools do I need to integrate with to generate a code health dashboard?▼

To generate a code health dashboard, you must integrate with a type checker, linter, test runner, dead code detector, and shell linter. The dashboard wraps these existing project tools to compute a single trackable health score.

Why does code quality drift as projects evolve and how do I catch regressions early?▼

Code quality drifts as projects evolve, but you can catch regressions early by computing a centralized weighted health score. This dashboard monitors health across CI pipelines to surface issues and guide quality improvements before they impact users.