health

Aggregate test outcomes, lint warnings, and dead code signals into a single health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive, auditable view of code quality by aggregating results from common project tools (type checker, linter, test runner, dead code detector, and shell lint) into a single, trackable health score and a trend history.

Core Features & Use Cases

  • Composite Health Score: Computes a weighted 0-10 score from multiple quality signals and persists weekly trends.
  • Tool Orchestration: Wraps existing project tooling (type checkers, linters, test runners, dead-code detectors, and shell linters) to deliver an integrated view.
  • Historical Insights: Maintains a local health history to identify regressions and improvements over time for engineering teams.
  • Use Case: A developer runs the health check before a release to ensure code quality thresholds are met and to communicate project health to teammates.

Quick Start

Run the health skill to generate a live dashboard of code quality scores for your project.

Frequently Asked Questions about health

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

FAQPage Schema
What is the best way to track code quality trends and detect regressions over time?

You can monitor code quality regressions by persisting weekly health scores in local storage. This trend analysis history enables teams to detect score drops over time and guide refactoring priorities before releases.

How do I set up a code quality dashboard before a software release?

A pre-release code quality dashboard orchestrates type checkers, linters, test runners, and dead code detectors to generate a live health score. This verifies quality thresholds are met and communicates project status to teammates.

Can I configure the scoring rubric for my specific code quality tools?

The code health scoring rubric is configurable, allowing you to adjust weights for test outcomes, lint warnings, and dead code signals. This lets you tailor the 0-10 score to prioritize specific quality metrics relevant to your project.

Does code health monitoring require external dependencies or cloud storage?

Code health monitoring uses standard local storage for history persistence and wraps existing project tooling, requiring no external dependencies or cloud storage. This keeps quality tracking self-contained within the local development environment.

How do I prioritize refactoring and testing efforts across a software project?

Refactoring and testing priorities are guided by the composite health score breakdown. By identifying which quality signals most heavily impact the score, developers can target the most critical issues first.