health

Runs project quality tools and computes a weighted 0-10 code health score.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill health-raghavbadhwar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/raghavbadhwar/rstack/tree/main/health
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill health-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lack a single, repeatable way to measure overall codebase quality, forcing them to run type checkers, linters, tests, and dead-code detectors separately and interpret scattered results. ## Core Features & Use Cases - Unified quality checks: Wraps the project's existing type checker, linter, test runner, dead code detector, and shell linter into one invocation. - Composite scoring: Computes a weighted 0-10 health score from the individual tool results and tracks the trend over time. - Use Case: Before a release, ask for a health check to run all quality gates at once, get a single score, and compare it against previous runs to confirm the codebase is improving rather than regressing. ## Quick Start Ask the agent to run a code health check and show the current quality score for this repository.

Frequently Asked Questions about health

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

FAQPage Schema
How do I check the overall code quality of my repository?

Invoke the health skill to run your project's type checker, linter, test runner, dead code detector, and shell linter in one pass. It combines the results into a weighted 0-10 score so you can judge overall codebase health at a glance.

How to track code quality trends over time?

The health skill records each computed composite score, letting you compare the current run against previous ones. Run it regularly, such as before releases, to see whether quality is improving or regressing.

What tools does a code health check run?

It wraps the tools already configured in the project: the type checker, linter, test runner, dead code detector, and shell linter. It does not install new tooling, so results reflect your existing setup.

Does the health check work in headless or CI sessions?

Yes, the preamble detects headless, spawned, and interactive session kinds and adjusts behavior accordingly. In headless runs it skips interactive prompts and proceeds with the checks, reporting results as prose.

Why is my code health score lower than expected?

The score is a weighted composite of each underlying tool's results, so failing tests, lint errors, type errors, or detected dead code all pull it down. Review the individual tool outputs in the report to identify which category is dragging the score.