health

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

1|Updated Jul 23, 2026
One-click install
npx skills add https://github.com/sanjanb/my-agent-harness --skill health-sanjanb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/sanjanb/my-agent-harness/tree/main/skills/health
Command: npx skills add https://github.com/sanjanb/my-agent-harness --skill health-sanjanb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lack a single, consistent view of codebase quality, forcing them to run type checkers, linters, tests, and dead-code detectors separately and interpret scattered results manually. ## Core Features & Use Cases - Unified Quality Dashboard: Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter) into one composite report. - Weighted Composite Score: Computes a 0-10 health score so quality is comparable across runs and projects. - Trend Tracking: Records scores over time so teams can see whether code health is improving or degrading. - Use Case: Before shipping a release, run the health check to confirm the codebase passes all checks and that the quality score has not regressed since the last sprint. ## Quick Start Ask the agent to run a code health check and show the current quality score for this codebase.

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 codebase?

Run the health skill, which executes your project's type checker, linter, test runner, dead code detector, and shell linter, then combines the results into a weighted 0-10 composite score with a dashboard view.

What tools does a code health dashboard aggregate?

This skill wraps the project's existing type checker, linter, test runner, dead code detector, and shell linter rather than installing new ones. It computes a weighted composite score from their outputs.

Can I track code quality trends over time?

Yes, the skill records health scores across runs so you can compare the current score against previous ones. This makes regressions visible before they accumulate into larger maintenance problems.

Does the health check work in headless or CI sessions?

Yes, the preamble detects the session kind (interactive, spawned, or headless) and adjusts behavior accordingly. In headless runs it skips interactive prompts and blocks on decisions that require a human answer.

When should I not rely on a composite quality score?

A composite score summarizes tool output but cannot judge architecture, design intent, or business logic correctness. Use it as a gate for mechanical quality, and pair it with code review for structural decisions.