health

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

Updated May 15, 2026
One-click install
npx skills add https://github.com/tgmarinho/canetaco --skill health-tgmarinho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/tgmarinho/canetaco/tree/main/.claude/skills/health
Command: npx skills add https://github.com/tgmarinho/canetaco --skill health-tgmarinho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams lack a single, objective view of codebase quality. This Skill wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter) into one dashboard that produces a weighted composite score and tracks quality trends over time. ## Core Features & Use Cases - Unified Quality Dashboard: Aggregates type checking, linting, tests, dead code detection, and shell linting into one report. - Weighted Composite Score: Computes a 0-10 health score so teams can quantify code quality at a glance. - Trend Tracking: Records scores over time to show whether the codebase is improving or degrading. - Use Case: Before a release, run a health check to confirm the codebase passes all quality gates and compare the current score against previous runs to catch regressions early. ## Quick Start Ask the assistant to run a code health check and show the 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 health of my codebase?

Run the health skill to execute your project's type checker, linter, test runner, dead code detector, and shell linter in one pass. It aggregates the results into a weighted composite score from 0 to 10 and shows trends over time.

What tools does a code quality dashboard typically run?

This dashboard wraps the tools already configured in your project: the type checker, linter, test runner, dead code detector, and shell linter. It does not install new tooling; it orchestrates and scores the output of what you already use.

How is the code quality score calculated?

The score is a weighted composite on a 0-10 scale, combining results from each underlying check such as type errors, lint violations, test failures, and dead code. Scores are stored so you can track quality trends across runs.

Can I track code quality trends over time?

Yes. Each health run records its score, letting you compare the current result against previous runs. This makes it easy to see whether recent changes improved or degraded overall codebase quality.

When should I run a health check instead of individual tools?

Run it when you want a single objective snapshot, such as before a release, during a review, or when onboarding to an unfamiliar repo. For fixing one specific failure, running the individual tool directly is faster.