health

Runs type checker, linter, tests, and dead code detection to compute a weighted code quality score.

1|Updated Aug 17, 2026
One-click install
npx skills add https://github.com/NalinDalal/skillset --skill health-nalindalal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/NalinDalal/skillset/tree/main/skills/workflow/health
Command: npx skills add https://github.com/NalinDalal/skillset --skill health-nalindalal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Getting a complete picture of codebase quality requires manually running the type checker, linter, test suite, and dead code detector, then mentally combining their results. This Skill automates that entire process and produces a single composite health score with prioritized recommendations. ## Core Features & Use Cases - Automatic Tool Detection: Detects available tools from project files (tsconfig.json, biome.json, eslint configs, pyproject.toml, Cargo.toml, go.mod) and runs only what exists. - Weighted Composite Scoring: Scores each category (type check 22%, lint 18%, tests 28%, dead code 13%, shell lint 9%) on a 0-10 scale and computes a weighted composite, redistributing weight for skipped tools. - Prioritized Recommendations: Ranks fixes by impact (weight times score deficit) so you know what to address first. - Use Case: Before a release, ask for a health check to get a dashboard showing tests at 10/10, lint at 6/10 with 12 warnings, and a composite score of 8.4/10 with recommendations ranked by impact. ## Quick Start Run a health check on this codebase and show me the quality dashboard with recommendations.

Frequently Asked Questions about health

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

FAQPage Schema
How do I check overall code quality in a project?▼

Run a health check that executes your type checker, linter, test suite, and dead code detector, then combines results into a weighted composite score. This Skill auto-detects tools like tsc, biome, eslint, ruff, pytest, and knip from your project config files.

How is the code health score calculated?▼

Each category is scored 0-10 based on error counts, then weighted: tests 28%, type check 22%, lint 18%, dead code 13%, shell lint 9%. Weights redistribute proportionally when a tool is unavailable, so skipped categories never count as failures.

Does the health check work with Python or Go projects?▼

Yes, it detects pyproject.toml for ruff and pytest, go.mod for go test, and Cargo.toml for cargo test alongside TypeScript tooling. It runs whichever tools your project actually uses rather than requiring a specific stack.

Will the health check fix the issues it finds?▼

No, it is strictly read-only by design. It produces the dashboard, raw failure output, and ranked recommendations so you can act on them, but it never modifies code or auto-fixes lint or test failures.

What happens if a tool like knip is not installed?▼

The category is skipped rather than scored as failed, and its weight is redistributed proportionally across the remaining categories. The composite score stays meaningful even with a partial toolchain.