health

Run type checking, linting, tests, dead-code detection, and shell linting to generate a composite 0-10 code-health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a messy, multi-tool quality workflow into a single code-health signal by running standard checks, combining them into a weighted 0-10 score, and recording results over time so you can see whether the codebase is getting healthier or drifting.

Core Features & Use Cases

  • Composite Code Quality Score (0–10): Wraps existing project tools (type checking, linting, tests, dead code detection, and shell linting) and computes a single weighted score to make health easy to compare across runs.
  • Trend Tracking Over Time: Stores health outputs and maintains longitudinal signals so you can spot regressions, improvements, and recurring hotspots instead of only reading one-off failures.
  • Health Check Triggers: Designed for common prompts like health check, quality dashboard, and how healthy is the codebase.

Quick Start

Run a full code quality health check by asking: "health check my codebase and give me the 0-10 quality score plus the main drivers and any trend changes since the last run."

Frequently Asked Questions about health

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

FAQPage Schema
How do I generate a single code quality score from multiple linting and testing tools?

A composite code-health score combines type checking, linting, tests, dead-code detection, and shell linting into a single weighted 0-10 value to make overall repository maintainability easy to compare.

Can I track code quality trends over time instead of just seeing one-off test failures?

Yes, code health trend tracking stores historical check outputs on disk, allowing you to spot regressions, improvements, and recurring quality hotspots over time rather than isolated incidents.

What is the best way to run a full codebase health check for a quality dashboard?

Running a full codebase health check executes standard project tools, computes a weighted quality score, and records the results, making it ideal for routine quality dashboard and maintainability evaluation tasks.

Does code quality scoring require Bash tooling integration to run project checks?

Yes, generating a code-health score requires Bash-capable tooling integration to execute the wrapped project checks and safely persist scoring and trend data to disk.

How do dead-code detection and type checking contribute to an overall quality score?

Dead-code detection and type checking act as weighted components within the composite scoring mechanism, where their individual results are combined to calculate the final 0-10 maintainability rating.

Why does my code quality trend analysis need to persist scoring data on disk?

Trend analysis requires on-disk persistence of historical health outputs to maintain longitudinal signals, enabling the detection of regressions and improvements across multiple runs.