health

Aggregate type checking, linting, testing, and dead-code analysis into a unified code-health score.

9|3|Updated Jan 29, 2022
One-click install
npx skills add https://github.com/I194/PMTools_2.0 --skill health-i194
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/I194/PMTools_2.0/tree/main/.claude/skills/gstack/health
Command: npx skills add https://github.com/I194/PMTools_2.0 --skill health-i194

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality monitoring is often a collection of disjoint checks. This Skill wraps your existing project tools (type checker, linter, test runner, dead code detector, and shell linter) into a single, weighted 0-10 health score and tracks trends over time.

Core Features & Use Cases

  • Unified health score: aggregates results from multiple tools into one actionable metric.
  • Trend tracking: visualizes health changes to reveal regressions early.
  • Deterministic checks: executes type checks, lint, tests, and dead-code analysis to surface concrete issues for developers.

Quick Start

Run the health dashboard to evaluate the current codebase health and surface improvements in one place.

Frequently Asked Questions about health

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

FAQPage Schema
How do I aggregate type checking, linting, and test results into a single code quality score?

A code health dashboard unifies disjoint quality checks by wrapping your existing project tools—type checker, linter, test runner, and dead code detector—to produce a single, weighted 0-10 health score and track historical trends.

What is the best way to track code health trends and catch regressions early in a multi-repo project?

Tracking code health trends across multi-repo projects requires a dashboard that visualizes historical changes in type checking, linting, and test results, revealing regressions early and providing an actionable health view for planning.

How do I visualize dead-code analysis and test coverage together for ongoing codebases?

You can visualize dead-code analysis and test coverage together by running a health dashboard that aggregates these deterministic checks into a unified summary, which can then be loaded into context for planning or code reviews.

Does this code health dashboard require specific lint or test runner integrations to work?

The dashboard requires integration with the repository's existing tooling, meaning it wraps your current type checker, linter, test runner, and dead code detector rather than running standalone checks.

Can I use a unified health score for sprint planning and code reviews?

Yes, you can use the unified health score for sprint planning and code reviews by loading the dashboard-like summary into context, which provides developers with a single actionable view of concrete issues to address.