health

Aggregates linting, typing, and test diagnostics into weighted 0-10 health score with trends.

Updated May 27, 2026
One-click install
npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill health-shmurdoc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/Shmurdoc/EasyRide-v1/tree/main/.opencode/skills/gstack-health
Command: npx skills add https://github.com/Shmurdoc/EasyRide-v1 --skill health-shmurdoc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running type checkers, linters, test runners, and dead code detectors manually across a project is time-consuming and produces fragmented results that are hard to compare. Teams need a single, actionable metric to understand code quality and track whether refactors and fixes are actually improving the codebase.

Core Features & Use Cases

  • Unified Quality Dashboard: Aggregates results from type checkers, linters, test runners, dead code detectors, and shell linters into one view.
  • Composite Scoring: Computes a weighted 0-10 score that reflects overall code health, making it easy to spot regressions or improvements.
  • Trend Tracking: Monitors score changes over time to measure the impact of engineering work and catch quality decay early.

Quick Start

Use the health skill to run all configured code quality checks and display the current composite health score for your project.

Frequently Asked Questions about health

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

FAQPage Schema
How do I get a single code quality score from multiple linters and type checkers?

Code quality scores aggregate diagnostics from type checkers, linters, test runners, and dead code detectors into a single weighted 0-10 metric. This unified dashboard replaces fragmented reports with one actionable health score for your project.

How does tracking code health trends over time work?

Tracking code health trends monitors score changes over time to measure the impact of engineering work and catch quality decay early. It produces historical trend data from aggregated diagnostics for continuous monitoring across your codebase.

Can I use a composite health score for pre-commit validation in a multi-language codebase?

Composite health scores apply to development workflows requiring pre-commit validation across multi-language codebases. The assessment requires project-specific tooling configurations to compute the weighted 0-10 score from various diagnostics.

What is the best way to automate a code quality audit across my project?

Automating a code quality audit aggregates results from type checkers, linters, test runners, dead code detectors, and shell linters into one view. This computes a weighted 0-10 score reflecting overall code health and produces historical trend data.

Do I need project-specific tooling configurations to run a code health check?

Project-specific tooling configurations are required to run a code health check. The assessment automates diagnostics from type checkers, linters, test runners, dead code detectors, and shell linters by aggregating their results into a single weighted composite score.