health

Produces a weighted 0-10 health score by wrapping type checking, linting, tests, dead code detection, and shell linting.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates the overhead of running multiple quality tools into a single, interpretable health score, helping teams understand code health at a glance without manual tallying.

Core Features & Use Cases

  • Wraps type checker, linter, test runner, dead code detector, and shell linter into one health assessment.
  • Produces a weighted 0-10 health score and tracks trends over time to surface improvement or regression.
  • Use in CI, on-demand repo health reviews, or before releases to identify hotspots and prioritize fixes.

Quick Start

Invoke the health workflow on your repository to generate a current health score and actionable hotspots.

Frequently Asked Questions about health

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

FAQPage Schema
How do I consolidate multiple static analysis and test execution results into a single code health score?

You can consolidate static analysis and test execution results by running a health workflow that wraps type checking, linting, dead code detection, and test execution to produce a weighted 0-10 code health score, highlighting trends and actionable hotspots.

What is the best way to track code health trends and identify hotspots in a CI pipeline?

Tracking code health trends in a CI pipeline is best achieved by running an automated health assessment that generates a weighted 0-10 score and contextual guidance, surfacing quality regressions and hotspots across multiple dimensions over time.

Does this code health monitoring approach require specific linters or test runners to be pre-configured?

This code health monitoring approach wraps existing type checking, test execution, dead code detection, and shell linting tools, requiring no specific external dependencies to generate a unified score and actionable maintenance recommendations.

Can I use a single quality dashboard score for on-demand repository health reviews before releases?

You can use a single quality dashboard score for on-demand repository health reviews before releases by invoking a health workflow that analyzes the codebase and returns a weighted 0-10 score with prioritized fix recommendations.

Why combine dead code detection and shell linting with standard type checking for repository health metrics?

Combining dead code detection and shell linting with standard type checking provides a comprehensive view of repository health metrics by consolidating multiple quality dimensions into a single interpretable score, reducing manual tallying overhead.