health

Calculate a weighted code quality score from linter, test, and static analysis results.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/yocxy2/gstack3 --skill health-yocxy2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/yocxy2/gstack3/tree/main/health
Command: npx skills add https://github.com/yocxy2/gstack3 --skill health-yocxy2

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of visibility into code quality by providing a unified, weighted health score that tracks technical debt and maintenance trends over time.

Core Features & Use Cases

  • Composite Scoring: Aggregates metrics from linters, test runners, and dead code detectors into a single 0-10 health index.
  • Trend Tracking: Monitors how your codebase quality evolves across commits and sessions.
  • Use Case: Use this before a major refactor to establish a baseline, or during a sprint to ensure that new features are not degrading overall system stability.

Quick Start

Run the health skill to generate a comprehensive quality report for the current 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 composite code quality score for my repository?

To calculate a composite code quality score, this skill aggregates results from linters, test runners, and dead code detectors into a unified 0-10 health index. It requires access to local shell tools and project-specific configuration files to compute the metrics.

What is a weighted code health index and how does it track technical debt?

A weighted code health index quantifies codebase health by integrating static analysis and test runner outputs. It tracks technical debt by monitoring how these maintenance metrics evolve across commits and development sessions over time.

How do I establish a code quality baseline before a major refactor?

You can establish a code quality baseline before a refactor by running the health skill to generate a comprehensive quality report. This captures your current technical debt and maintenance trends as a reference point for future commits.

Can I use local linters and test runners to monitor codebase health during a sprint?

Yes, you can use local linters and test runners to monitor codebase health during a sprint. The skill integrates these local tool results to ensure new features are not degrading overall system stability.

What do I need to compute code health metrics for my software project?

To compute code health metrics, you need local shell tools and project-specific configuration files for your linters and test runners. The skill uses these dependencies to execute static analysis and log your quality scores.