health

Aggregate code quality tool outputs into a weighted 0-10 health score and trend report.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aggregates multiple code quality tools into a single health score and trend report, giving a clear view of overall code health.

Core Features & Use Cases

  • Wraps a type checker, linter, test runner, dead code detector, and shell linter into a unified dashboard.
  • Computes a weighted 0-10 health score and tracks trends over time, highlighting regression areas.
  • Use cases include CI pipeline health checks, on-demand code quality reviews, and project health reporting for leadership.

Quick Start

Run the health check to generate the latest code quality dashboard 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 aggregate code quality tools into a single dashboard for CI pipelines?

You can aggregate code quality tools into a single dashboard by wrapping a type checker, linter, test runner, dead code detector, and shell linter to compute a weighted 0-10 health score and generate trend reports for your CI pipeline.

What is a code health score and how does it track refactoring trends?

A code health score is a weighted 0-10 metric that aggregates multiple code quality tool outputs to track trends over time, highlighting regression areas to guide your refactoring efforts and project health reporting.

Do I need a type checker and dead code detector to run code health checks?

Yes, running code health checks requires data from a type checker, linter, test runner, dead code detector, and shell linter to aggregate the results into a unified weighted 0-10 health score and trend report.

Can I use a code quality dashboard for local development or is it only for CI?

You can use a code quality dashboard for both local development and CI pipelines to run health checks, detect regressions, and guide refactors on-demand or automatically during continuous integration.

What's the best way to detect code quality regressions across multiple linting tools?

The best way to detect regressions is to aggregate linter, type checker, and test runner outputs into a unified health score that tracks historical trends, automatically highlighting areas where code quality has degraded.

How does a weighted code health score handle conflicting results from different quality tools?

A weighted code health score resolves conflicting quality tool results by applying weights to outputs from the type checker, linter, test runner, dead code detector, and shell linter, aggregating them into a single 0-10 metric.