health

Aggregate code-quality tool results into a weighted 0-10 health score.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gfires/motion-analysis --skill health-gfires
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/gfires/motion-analysis/tree/main/health
Command: npx skills add https://github.com/gfires/motion-analysis --skill health-gfires

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality dashboards compile metrics across type checking, linting, tests, dead code, and shell hygiene to give a single, understandable health score.

Core Features & Use Cases

  • Aggregates results from type checkers, linters, test runners, dead code detectors, and shell linters into a weighted 0-10 score.
  • Tracks health trends over time and per-branch to surface regressions and improvements.
  • Provides a read-only dashboard for CI and developers to decide where to focus quality efforts.

Quick Start

Run the health skill to generate a current health snapshot 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 aggregate code quality metrics into a single repository health score?▼

To aggregate code quality metrics into a repository health score, you can use a dashboard that wraps type checkers, linters, test runners, and dead code detectors to compute a weighted 0-10 composite score. It tracks health trends across branches over time.

What is included in a code health dashboard for CI pipelines?▼

A code health dashboard for CI pipelines includes type checking, linting, test execution, dead code detection, and shell linting results. It aggregates these tool outputs into a weighted 0-10 score to surface actionable insights without modifying your codebase.

Can I track dead code and linting regressions over time per branch?▼

Yes, you can track dead code and linting regressions per branch. The dashboard computes per-tool results for each run, enabling trend tracking across branches and over time to highlight quality improvements and regressions for release planning.

How do I run multiple code quality tools without modifying my source code?▼

To run multiple code quality tools without modifying source code, this dashboard executes type checkers, linters, and dead code detectors in a read-only mode. It aggregates the per-tool results into a composite 0-10 score to guide development focus.

Does the code health dashboard automatically fix linting or type checking errors?▼

No, the code health dashboard does not automatically fix linting or type checking errors. It operates as a read-only tool that runs quality checks, computes a weighted 0-10 score, and surfaces actionable insights for developers to address manually.

When should I use a composite code health score in my development workflow?▼

You should use a composite code health score during CI pipelines, local development, and release planning. It aggregates type checking, linting, tests, and dead code detection into a single metric, helping you track quality trends and decide where to focus efforts.