health

Aggregate type safety, lint, tests, dead code, and shell hygiene into a 0-10 score.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/rahmanayon/beehive --skill health-rahmanayon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/rahmanayon/beehive/tree/main/.claude/skills/gstack/health
Command: npx skills add https://github.com/rahmanayon/beehive --skill health-rahmanayon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code quality dashboard that wraps type checker, linter, test runner, dead code detector, and shell linter. It computes a weighted 0-10 score and tracks trends over time.

Core Features & Use Cases

  • Aggregates multiple project-quality tools (type checker, linter, test runner, dead code detector, shell linter) into a single health score.
  • Tracks code health trends over time to reveal improvements or degradations and guide fixes.
  • Use cases include evaluating a codebase after refactors, before releases, or during CI to surface actionable quality signals.

Quick Start

Run the health skill to generate and view the current code health dashboard for the repository.

Frequently Asked Questions about health

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

FAQPage Schema
How do I calculate a code quality score for my repository?

To calculate a code quality score, this skill aggregates type safety, lint cleanliness, test coverage, dead code, and shell hygiene into a single weighted 0-10 score. It wraps existing type checkers, linters, and test runners to compute the overall health metric.

How do I track code health trends over time during CI?

You can track code health trends over time by running this skill during your continuous integration workflows. It stores historical score data to reveal quality improvements or degradations, guiding ongoing improvement efforts across your CI pipeline.

What is the best way to aggregate lint and test coverage metrics into one dashboard?

The best way to aggregate lint and test coverage metrics is using a dashboard that integrates multiple project-quality tools. This skill wraps type checkers, linters, test runners, dead code detectors, and shell linters to surface a unified code health score.

Does this code health dashboard require specific dependencies to run?

No specific dependencies are required to run this code health dashboard. It integrates existing project-quality tools already present in your environment, such as your type checker, linter, test runner, dead code detector, and shell linter, to compute the weighted score.

When should I monitor code health for releases?

You should monitor code health before releases to ensure type safety, test coverage, and lint cleanliness meet standards. This skill generates a current code health dashboard and provides actionable recommendations to guide final pre-release fixes.