health

Compute a weighted 0-10 code health score from type, lint, test, and dead code checks.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/devs6186/claude-private-skills-agents-commands --skill health-devs6186
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/devs6186/claude-private-skills-agents-commands/tree/main/skills/gstack/health
Command: npx skills add https://github.com/devs6186/claude-private-skills-agents-commands --skill health-devs6186

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality health visibility across a project. This Skill wraps tools such as a type checker, linter, test runner, dead code detector, and shell linter to compute a weighted 0-10 score and track trends over time, helping teams understand where to focus improvements.

Core Features & Use Cases

  • Unified health score: a single, interpretable metric that aggregates results from multiple quality checks.
  • Trend tracking: visualize improvements and regressions over time to guide refactoring and testing.
  • Actionable guidance: identify hotspots and recommended next steps to reduce defects and debt.

Quick Start

Run the health scan to generate the current code health score and trend report for your repository.

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 health score for my repository?

Code health tracking monitors quality trends over time by running a type checker, linter, and test runner to compute a weighted 0-10 score. This helps teams visualize improvements and regressions to guide refactoring and testing efforts.

Can I track code quality trends over time for my dashboards?

Yes, you can track code quality trends over time because the workflow stores time-series health data. This stored data is designed for consumption by downstream dashboards to visualize improvements and regressions across project sizes.

Does this code health calculator work across different language ecosystems?

Yes, the code health calculator works across language ecosystems and project sizes. It orchestrates various quality tools, including a type checker, linter, test runner, dead code detector, and shell linter, to compute the composite score.

What is the best way to identify code quality hotspots and reduce technical debt?

The best way to identify code quality hotspots is by running a health scan to generate a trend report and composite score. This provides actionable guidance and recommended next steps to reduce defects and technical debt.