health

Orchestrate type checks, linting, tests, dead code analysis, and shell hygiene into a weighted 0-10 health score.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/bizzybae/qstack --skill health-bizzybae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/bizzybae/qstack/tree/main/gstack-original/health
Command: npx skills add https://github.com/bizzybae/qstack --skill health-bizzybae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality gaps slow delivery and obscure risk. This Skill collects type checks, lint results, test outcomes, dead code signals, and shell hygiene into a single, understandable health score to help teams quantify and improve their codebase health.

Core Features & Use Cases

  • Wraps a suite of project tools (type checker, linter, test runner, dead code detector, shell linter) to compute a weighted 0-10 health score.
  • Tracks health trends over time and surfaces actionable insights to guide refactors and process improvements.
  • Use case: run in CI to surface regressions, prioritize fixes, and communicate health to stakeholders.

Quick Start

Run a full health check across the repository to generate a current health score.

Frequently Asked Questions about health

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

FAQPage Schema
How do I calculate a code health score across my CI pipeline?

Calculate a code health score by orchestrating type checking, linting, tests, dead code analysis, and shell hygiene checks into a weighted 0-10 score. This approach wraps existing project tools to quantify codebase health across languages and CI pipelines.

What is the best way to track code quality trends over time in a repository?

Track code quality trends by computing a weighted health score from static analysis and test outcomes, then maintaining historical health data. This enables trend tracking and surfaces actionable insights to guide refactors and process improvements over time.

Can I use static analysis and dead code detection to surface CI regressions?

Yes, you can use static analysis and dead code detection to surface CI regressions. By running a full health check in CI, you can identify type checking failures, lint violations, and dead code signals to prioritize fixes and communicate risk to stakeholders.

Does this code health scoring approach work for ongoing codebases across multiple languages?

Yes, this code health scoring approach targets ongoing codebases across multiple languages. It works by wrapping a suite of existing project tools rather than relying on a language-specific analyzer, enabling broad health visibility across diverse repositories.

How do I generate a dashboard-friendly code quality score for stakeholders?

Generate a dashboard-friendly code quality score by wrapping your test runner, linter, and type checker to compute a weighted 0-10 score. This exposes a single, understandable health metric to communicate codebase health to stakeholders.

Why do I need a weighted code health score instead of just checking if tests pass?

You need a weighted code health score because passing tests alone obscure risk from dead code, lint violations, and shell hygiene gaps. A 0-10 score collects these signals into a single metric to help teams quantify and improve their codebase health.