skills.rest
JeremiahEllington
JeremiahEllingtonCOMMUNITY
Explore all skills by this author →
GitHub

health

Consolidate code-quality signals from multiple tools into a 0-10 health score.

Updated Apr 6, 2026
Search Tags:#metrics#dashboard#code-quality#health#tools#ci
One-click install
npx skills add https://github.com/JeremiahEllington/NoahEllington --skill health-jeremiahellington
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/JeremiahEllington/NoahEllington/tree/main/.claude/skills/health
Command: npx skills add https://github.com/JeremiahEllington/NoahEllington --skill health-jeremiahellington

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the collection and scoring of code quality signals from multiple tools to produce a single health score. This helps teams understand the health of their codebase at a glance and pinpoint areas to improve.

Core Features & Use Cases

  • Orchestrates type checker, linter, test runner, dead code detector, and shell linter to compute a weighted 0-10 health score.
  • Tracks health trends over time per repository or branch, so you can see improvement or regression.
  • Provides actionable guidance based on the score breakdown to prioritize fixes and improvements.

Quick Start

Run a full health check to generate the dashboard 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 consolidate code quality signals from a linter and test runner into a single score?▼

Consolidate code quality signals by orchestrating type checkers, linters, test runners, dead code detectors, and shell linters to compute a weighted 0-10 health score. This single score helps pinpoint specific areas needing fixes across the codebase.

Can I track codebase health trends over time per branch?▼

Track codebase health trends over time per repository or branch. The dashboard records historical metrics from type checks, linting, and tests, allowing you to monitor improvement or regression as your codebase evolves.

Do I need a dead code detector and shell linter to generate a code quality dashboard?▼

A dead code detector and shell linter are required to generate the code quality dashboard. The scoring system orchestrates these tools alongside type checkers, linters, and test runners to produce a complete weighted health score.

What is the best way to automate codebase health checks for CI pipelines?▼

Automate codebase health checks by orchestrating multiple quality tools to output a 0-10 score with historical trends. This provides actionable guidance based on the score breakdown to prioritize fixes and improvements within your CI workflow.

How does the weighted 0-10 code health score work?▼

The weighted 0-10 code health score works by aggregating outputs from type checks, linting, tests, dead code detection, and shell hygiene. It breaks down these signals to provide actionable guidance for prioritizing codebase improvements.

Why use an automated code health score instead of separate linting and test reports?▼

An automated code health score consolidates separate tool reports into a single dashboard. Instead of reviewing isolated metrics, teams get a unified 0-10 score with trend tracking that provides actionable guidance to prioritize fixes.

Related Skills

Explore More Software Engineering Skills→
yckkkkyckkkk
1

health

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

Community
Advanced
kunalrawat425kunalrawat425

health

Aggregate type checks, linting, tests, and dead-code detection into a weighted 0-10 health score.

Community
Intermediate
23000311472300031147

health

Aggregate code quality metrics into a weighted 0-10 health score dashboard.

Community
Intermediate
GTC6244GTC6244

health

Aggregate type-checks, lint, tests, dead code, and shell hygiene into a single score.

Community
Advanced