health

Aggregate static analysis and test results into a 0-10 health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized health view of your codebase by aggregating results from static analysis, tests, and other quality checks into a single, interpretable score and trend history.

Core Features & Use Cases

  • Unified health score: weights results from type checkers, linters, test runners, dead code detectors, and shell linting to produce a single 0-10 score.
  • Trend tracking: preserves health over time to spot regressions and improvements.
  • Use Case: run this dashboard after a CI run to quickly assess overall health and identify failing areas.

Quick Start

Run the health check to generate or update the health dashboard with the latest project metrics.

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 health score?

To aggregate code quality metrics into a single health score, weight results from type checkers, linters, dead code detectors, and test runners to produce a unified 0-10 rating. This approach provides a centralized view of your codebase's overall condition.

What is a code health dashboard used for?

A code health dashboard is used to provide a centralized view of your codebase by aggregating static analysis and test results. It helps you quickly assess overall quality, identify failing areas, and monitor ongoing improvements.

How do I track code quality trends over time?

You track code quality trends over time by preserving historical health data after each CI run. This allows you to spot regressions and improvements, generating dashboard-ready reports for ongoing quality visibility.

Can I weight static analysis and test results differently in a code health check?

Yes, you can weight static analysis and test results differently in a code health check. The scoring supports per-tool weighting, allowing you to customize the impact of linters, type checkers, and dead code detectors on the final score.

When do I need to run a code health dashboard?

You need to run a code health dashboard after a CI run to quickly assess your project's overall health and identify failing areas. It is ideal for codebases requiring quick health checks and ongoing quality visibility.

What tools should I integrate for a comprehensive code quality score?

To get a comprehensive code quality score, integrate type checkers, linters, test runners, dead code detectors, and shell linting tools. The dashboard aggregates these varied results to compute the final 0-10 health rating.