health

Run code quality checks and generate a composite health dashboard.

Updated Apr 1, 2026

Search Tags:#metrics #dashboard #code-quality #lint #ci #dead-code #type-check

Ready to run

npx skills add https://github.com/bajajvinamr/little-wins --skill health-bajajvinamr

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: health
Source: https://github.com/bajajvinamr/little-wins/tree/main/.claude/skills/gstack/health
Command: npx skills add https://github.com/bajajvinamr/little-wins --skill health-bajajvinamr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a centralized view of code quality by coordinating type checks, linters, test runners, and dead-code detectors to surface trends and actionable insights across a codebase.

Core Features & Use Cases

Consolidated health metrics across type safety, lint, tests, and dead code.
Trend analysis over time for multi-repo projects and CI pipelines.
Use Case: A team wants a weekly health digest to identify flaky tests and rising lint errors before release.

Quick Start

Run the health workflow to generate a live code-quality dashboard for the current project.

Frequently Asked Questions about health

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

FAQPage Schema

How do I track code quality metrics across multiple repositories in a CI pipeline?▼

You can track code quality across multiple repos by orchestrating type checks, linters, test runners, and dead-code detectors to compute a composite score. This generates a centralized dashboard and trend analysis suitable for CI pipelines and developer workflows.

How does a code quality health dashboard identify regressions over time?▼

A code quality health dashboard identifies regressions by running a suite of checks including type safety, lint, tests, dead code, and shell hygiene. It computes a composite score and visualizes trend analysis to surface actionable insights across branches and multi-repo projects.

Can I use this code health monitoring workflow for both production apps and libraries?▼

Yes, you can apply this code health monitoring workflow to production apps and libraries. It coordinates type checks, linters, test runners, and dead-code detectors to monitor health over time and identify regressions across various project types.

What is the best way to consolidate type safety, lint, and dead code checks into one dashboard?▼

The best way to consolidate type safety, lint, and dead code checks is to run a coordinated health workflow. It orchestrates these tools, computes a composite score, and presents a live code-quality dashboard to surface actionable trends and insights.

How do I generate a weekly health digest to catch flaky tests and rising lint errors before release?▼

Generate a weekly health digest by running the health workflow to orchestrate test runners and linters. It tracks trend analysis over time, computing a composite score to identify flaky tests and rising lint errors before release.

Do I need to install external dependencies to run dead-code detection and type checks?▼

No external dependencies are required to run dead-code detection and type checks. The skill operates independently without dependencies, orchestrating its suite of checks including type safety, lint, tests, dead code, and shell hygiene to compute its composite score.