gs:health

Compute a weighted composite codebase health score from type checker, linter, and test runner results.

34|6|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-health
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gs:health
Source: https://github.com/thanh-abaii/gstack-windows-port/tree/main/skills/gstack-health
Command: npx skills add https://github.com/thanh-abaii/gstack-windows-port --skill gs-health

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive overview of the codebase's health by computing a weighted composite score, enabling developers to quickly identify areas for improvement.

Core Features & Use Cases

  • Code Quality Dashboard: Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter).
  • Composite Score: Computes a 0-10 score based on various checks.
  • Trend Tracking: Tracks health trends over time.
  • Use Case: Use the skill when performing regular health checks, conducting code reviews, or preparing for code audits.

Quick Start

Run the 'gs:health' skill to assess the current health of your codebase.

Frequently Asked Questions about gs:health

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

FAQPage Schema
How do I monitor codebase health with a composite score?

To monitor codebase health, this Skill computes a 0-10 weighted composite score by aggregating results from type checkers, linters, and test runners. It provides a dashboard overview to help you quickly identify areas for improvement during routine maintenance.

What is a weighted composite score for code quality?

A weighted composite score for code quality is a 0-10 metric calculated by aggregating outputs from various project tools. It summarizes overall codebase health, enabling developers to track health trends over time and prepare for code audits.

Can I use existing linters and type checkers for a code health dashboard?

Yes, you can use existing linters and type checkers. The Skill wraps your current project tools, including type checkers, test runners, dead code detectors, and shell linters, to generate a unified code quality dashboard and calculate the composite score.

Does the code health check require integration with test runners and linters?

Yes, integration with test runners, type checkers, and linters is required. The Skill relies on these existing project tools to gather the raw data necessary to compute the weighted composite score and track codebase health trends over time.

When should I perform a codebase health check?

You should perform a codebase health check when conducting regular maintenance, performing code reviews, or preparing for code audits. The Skill tracks health trends over time, helping you identify areas for improvement during these routine development activities.

What's the best way to assess code quality for an audit?

The best way to assess code quality for an audit is to run a comprehensive health check that aggregates results from type checkers, linters, and test runners into a single 0-10 composite score. This provides a clear dashboard overview of codebase health.