health

Run project-quality tools and produce a weighted 0-10 code health score.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/steadyfall/fspeek --skill health-steadyfall
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/steadyfall/fspeek/tree/main/.claude/skills/gstack/health
Command: npx skills add https://github.com/steadyfall/fspeek --skill health-steadyfall

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code bases accumulate health debt; this Skill wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), to compute a weighted composite 0-10 health score and track trends over time, surfacing quality risks automatically.

Core Features & Use Cases

  • End-to-end health metric: orchestrates type checking, linting, tests, dead code detection, and shell linting to produce a single health score.
  • Trend tracking: stores historical scores to surface deterioration or improvement over time.
  • Project-wide guidance: signals when health drops and suggests concrete actions to improve quality.

Quick Start

Run the health check to compute the initial code health score 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 composite code quality score from multiple project tools?

Track code health trends by storing historical weighted scores from type checking, linting, tests, dead code detection, and shell linting. This historical context surfaces quality risks automatically, allowing you to monitor deterioration or improvement over time across builds and releases.

What is a weighted code health score and how does it surface quality risks?

A weighted code health score is a 0-10 metric that aggregates type checking, linting, test, dead code, and shell lint results. It surfaces quality risks by tracking historical trends and signaling when health drops, suggesting concrete actions to improve quality.

How do I automate code health assessment for ongoing software projects?

Automate code health assessment by running multiple project-quality tools together to produce a weighted 0-10 score. This applies to ongoing software projects to monitor health across builds, PRs, and releases, enabling continuous trend analysis over time.

Does this code health monitoring approach require specific tools to be set up?

Yes, this approach wraps existing project tools, requiring a type checker, linter, test runner, dead code detector, and shell linter to be configured. It orchestrates these existing tools to compute the composite health score and track trends.

What's the best way to monitor code base health debt over time?

The best way to monitor code base health debt is by computing a weighted 0-10 health score from existing project tools and tracking it historically. This surfaces quality risks automatically, signaling drops and suggesting concrete actions to improve quality.