health

Compute a weighted 0-10 code quality score from project tools and track trends.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codebases accumulate undetected quality issues. This skill runs a suite of project tools (type checker, linter, test runner, dead code detector, and shell linter), computes a weighted 0-10 quality score, and tracks health trends over time.

Core Features & Use Cases

  • Composite health score: wraps multiple quality tools to generate a single score.
  • Trend tracking: records health over time to spot improvements or regressions.
  • CI/local workflow: integrates into CI or local development to provide a ready health view.

Quick Start

Run a health check to see the current health score and trends for your codebase.

Frequently Asked Questions about health

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

FAQPage Schema
How do I compute a composite code quality score from multiple lint and test tools?

A composite code quality score is computed by orchestrating your type checker, linter, test runner, dead code detector, and shell linter to generate a single weighted 0-10 health metric. This provides a holistic view of code health across runs and commits.

Can I track code quality trends over time in my CI pipeline?

Yes, you can track code quality trends over time by applying this in CI pipelines. It records health data across runs and commits, allowing you to easily spot improvements or regressions in your codebase over time.

What is a weighted code health score and how does it work?

A weighted code health score is a 0-10 metric generated by wrapping multiple project quality tools. It aggregates results from type checking, linting, testing, and dead code detection to produce a single representative quality score.

Does the code quality dashboard work across different languages and tool configurations?

Yes, the code quality dashboard works across languages and tool configurations. It wraps existing project tools regardless of language, producing a unified 0-10 health score and tracking trends for ongoing monitoring.

How do I monitor dead code and type-check results together locally?

You can monitor dead code and type-check results together locally by running a health check during local development. It orchestrates your existing project tools to produce a holistic health score and store trend data.

What is the best way to visualize lint and test regressions across commits?

The best way to visualize lint and test regressions across commits is by tracking health trends over time. This approach records your weighted 0-10 quality score across runs, providing a clear dashboard view of regressions or improvements.