health

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

Updated May 9, 2026
One-click install
npx skills add https://github.com/kk20300113-png/my-claude-skills --skill health-kk20300113-png
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/kk20300113-png/my-claude-skills/tree/main/health
Command: npx skills add https://github.com/kk20300113-png/my-claude-skills --skill health-kk20300113-png

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running separate code quality tools (type checkers, linters, test runners, dead code detectors) gives fragmented results with no unified view of your project's overall health or historical progress across commits and releases.

Core Features & Use Cases

  • Unified Tool Orchestration: Wraps your project's existing type checker, linter, test runner, dead code detector, and shell linter into a single, repeatable workflow.
  • Composite Quality Scoring: Computes a weighted 0-10 score that aggregates results from all quality checks into an easy-to-understand health metric.
  • Trend Tracking: Monitors quality scores over time to show if your codebase is improving, degrading, or staying stable across development cycles.
  • Use Case: Before a major release, run this skill instead of manually executing 5+ separate quality tools and calculating an overall score yourself.

Quick Start

Request a full code health check for your active project to get your unified quality score and historical trend data.

Frequently Asked Questions about health

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

FAQPage Schema
How do I calculate a unified code quality score from multiple static analysis and testing tools?

To calculate a unified code quality score, this skill aggregates results from your existing type checkers, linters, test runners, and dead code detectors into a weighted composite 0-10 metric. It replaces fragmented manual assessment workflows with a single health score.

What is the best way to track codebase health trends across project commits?

Tracking codebase health trends across commits requires persistent monitoring of quality metrics over time. This skill monitors your weighted 0-10 quality score throughout development cycles to show whether your codebase is improving, degrading, or staying stable.

Can I run a pre-release code health check without manually executing multiple linters?

You can run a pre-release code health check without manually executing multiple linters by using this skill's unified tool orchestration. It wraps your project's existing type checker, linter, test runner, and dead code detector into a single repeatable workflow.

Does this code quality scoring approach work with my existing linting and type checking setup?

This code quality scoring approach works directly with your existing linting and type checking setup. It orchestrates your currently installed standard quality tools rather than replacing them, requiring no additional dependencies to compute the composite score.

Why use a composite quality score instead of separate static analysis outputs?

Using a composite quality score instead of separate static analysis outputs provides a unified view of your project's overall health. Separate tools yield fragmented results, whereas a weighted 0-10 metric offers an easy-to-understand health assessment for routine checks.

What specific code quality tools are needed to generate the 0-10 health metric?

To generate the 0-10 health metric, you need standard code quality tools including a type checker, linter, test runner, dead code detector, and shell linter. The skill orchestrates these existing tools to produce the automated quality score.