health

Aggregate type checking, lint, test, and dead code scores into a health trend log.

1|Updated Mar 15, 2026

Search Tags:#dashboard #code-quality #health #lint #tests #type-check #trend

Ready to run

npx skills add https://github.com/westn/gstack-pi-port --skill health-westn

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: health
Source: https://github.com/westn/gstack-pi-port/tree/main/port/gstack/health
Command: npx skills add https://github.com/westn/gstack-pi-port --skill health-westn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality dashboards bring all tools into a single view to help teams understand health at a glance and act quickly.

Core Features & Use Cases

Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter) into a single health score.
Computes a weighted 0-10 score and tracks trends over time.
Use in CI dashboards or local workflows to monitor health and drive improvements.

Quick Start

Run the health skill to generate a dashboard for your repository and start tracking health over time.

Frequently Asked Questions about health

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

FAQPage Schema

How do I aggregate type checking, lint, and test results into a single code quality score?▼

You can aggregate code quality by wrapping tools like tsc, biome, bun, knip, and shellcheck into a single weighted 0-10 score. It reads tool outputs directly and computes an overall health score for your codebase.

What is the best way to track codebase health trends over time in a CI dashboard?▼

Tracking codebase health trends involves logging a computed health score history over time. This skill emits a health history log alongside per-tool scores, enabling CI dashboards and local workflows to monitor project health.

Does this code health tracker work with my existing linter and dead code detector?▼

Yes, the code health tracker works with existing project tools by configuring and reading outputs from tsc, biome, bun, knip, and shellcheck. It wraps these tools to compute per-tool scores and an overall health score.

Can I use a weighted health score to monitor type checking and dead code detection locally?▼

Yes, you can use a weighted 0-10 health score to monitor type checking and dead code detection locally. It computes scores per tool, including knip for dead code and tsc for type checking, suitable for local workflows.

What tools do I need to configure before generating a code quality dashboard?▼

You need to configure standard project tools like tsc, biome, bun, knip, and shellcheck. The skill reads outputs from these tools to emit per-tool scores, an overall score, and a health history log for your dashboard.

How does dead code detection factor into an overall code health score?▼

Dead code detection factors into the overall code health score through knip outputs. The skill reads knip results alongside lint, test, and type check outputs to compute a weighted 0-10 score reflecting project-wide health.