health

Run quality tools to compute a weighted 0-10 code health score.

Updated Apr 24, 2026
One-click install
npx skills add https://github.com/MissTully/Gstack --skill health-misstully
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/MissTully/Gstack/tree/main/health
Command: npx skills add https://github.com/MissTully/Gstack --skill health-misstully

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality can be hard to gauge across multiple tools. This Skill provides a single, consistent health score by wrapping type checker, linter, test runner, dead code detector, and shell linter, and tracks trends over time to reveal improvements or regressions.

Core Features & Use Cases

  • Wraps common project tools (type checker, linter, test runner, dead code detector, shell linter) into a unified health signal.
  • Computes a weighted 0-10 score and stores historical trends for monitoring code health across time.
  • Use cases include pre-merge health checks, CI dashboards, and weekly codebase health reviews.

Quick Start

Run the health check to generate and view the current code quality score and trend report.

Frequently Asked Questions about health

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

FAQPage Schema
How do I compute a single code quality score from multiple tools?

To compute a single code health score, this Skill wraps your type checker, linter, test runner, dead code detector, and shell linter into a weighted 0-10 scoring model. It loads the necessary tool outputs to produce a reproducible code quality signal.

Can I track code health trends over time for CI dashboards?

Yes, you can track code health trends over time for CI dashboards. The Skill stores a time-based history of the computed 0-10 health score to reveal improvements or regressions across your codebase.

What's the best way to automate pre-merge code health checks?

The best way to automate pre-merge code health checks is using a Skill that runs all checks and generates a unified score. This tool executes common quality tools and outputs a reproducible health signal for your review scenarios.

How does the weighted code health scoring model work?

The weighted code health scoring model works by running a type checker, linter, test runner, dead code detector, and shell linter, then aggregating their outputs into a single 0-10 score. It keeps a time-based history to show trends.

Do I need to configure specific linters to use this code health check tool?

You need common project quality tools like a type checker, linter, test runner, dead code detector, and shell linter available in your environment. The code health check tool wraps these existing tools to compute its score without requiring external dependencies.

Why use a unified code health score instead of checking individual tool outputs?

A unified code health score solves the difficulty of gauging code quality across multiple tools. Instead of checking individual outputs, it wraps your type checker, linter, and test runner into a single consistent signal with historical trend tracking.