health

Compute a weighted 0-10 health score from project tool results.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool automates the assessment of codebase health by wrapping existing project tooling (type checkers, linters, test runners, dead-code detectors, and shell linters) to produce a single, weighted 0-10 health score and to track health trends over time.

Core Features & Use Cases

  • Weighted health scoring: combines results from type checking, linting, tests, and dead-code analysis into a single score from 0 to 10.
  • Trend tracking: maintains historical health data to identify regressions or improvements across commits and over time.
  • Quick health checks and dashboards: provides a unified view to inform maintenance, refactoring, and release readiness.

Quick Start

Run the health check to generate the latest project health dashboard.

Frequently Asked Questions about health

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

FAQPage Schema
How do I calculate a weighted code health score for my repository?

To calculate a weighted code health score, this skill wraps existing project tooling like type checkers, linters, test runners, and dead-code detectors to combine their results into a single 0-10 metric. It aggregates existing tool outputs into a unified quantitative score.

What is automated codebase health tracking and how does trend analysis work?

Automated codebase health tracking records your 0-10 health score over time. Trend analysis maintains historical health data across commits and branches to identify regressions or improvements, providing a unified view for proactive maintenance.

Can I use existing project tools like linters and type checkers for code health checks?

Yes, you can use existing project tools for code health checks. The skill wraps your current type checker, linter, test runner, dead-code detector, and shell linter to compute a composite score without replacing your configured toolchain.

How do I generate a code health dashboard for proactive maintenance?

You generate a code health dashboard by running an on-demand health check against your software repository. This produces a unified view of your weighted scores and historical trend data to inform refactoring and release readiness.

Does the code health score require external dependencies to run?

No, the code health score does not require external dependencies to run. The skill operates without additional dependency installation, relying entirely on wrapping the existing project tooling already configured in your software repository.