health

Aggregate type safety, lint, test coverage, dead code, and script hygiene into a 0-10 health score.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Software teams need a single, trustworthy view of code health across a complex gstack setup. This Skill aggregates type safety, lint cleanliness, test coverage, dead code detection, and shell hygiene into a cohesive dashboard to help engineering teams ship with confidence.

Core Features & Use Cases

  • Centralized health scoring: computes a weighted 0-10 score from multiple quality signals and tracks trends over time.
  • CI-friendly insights: integrates with pipelines to surface health status for quick risk assessment.
  • Cross-project visibility: supports mono-repos and multi-package ecosystems to surface hotspots and drift.

Quick Start

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

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 coverage into a single code quality score?

Code quality scoring aggregates type safety, lint cleanliness, test coverage, dead code, and script hygiene into a single weighted 0-10 score. This centralizes multiple quality signals into one actionable metric for engineering teams to track project health trends over time.

Can I use a code health dashboard for mono-repo and multi-package CI pipelines?

Yes, a code health dashboard supports mono-repos and multi-package ecosystems within CI pipelines. It surfaces project hotspots and quality drift across multiple packages, providing cross-project visibility to help teams assess release risks quickly during continuous integration.

What is the best way to track code quality trends across continuous integration builds?

Tracking code quality trends across CI builds involves logging a computed health score over time. By coordinating tools like tsc, ESLint, test runners, and dead code detectors, teams generate a portable dashboard that visualizes quality degradation or improvement across successive pipeline runs.

Does dead code detection and script hygiene factor into overall project health scoring?

Dead code detection and script hygiene are explicit components of overall project health scoring. The calculation applies a weighted formula that combines these signals with type safety, lint cleanliness, and test coverage to compute a comprehensive 0-10 score.

How do I generate a health score for a gstack project?

Generating a health score for a gstack project involves running the health skill to coordinate quality tools like tsc and biome. It computes a 0-10 score from multiple signals and produces a live dashboard showing type safety, lint, coverage, and dead code metrics.

What are the limitations of using a weighted 0-10 score for code health monitoring?

A weighted 0-10 score for code health monitoring aggregates multiple signals but relies on predefined weights for type safety, lint, coverage, and dead code. Teams with unique quality priorities may need to adjust these weights, as a single score can obscure specific failing metrics within mono-repos.