health

Execute type checkers, linters, test runners, and dead code detectors to report codebase health.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires type checker, linter, test runner, dead code detector, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a comprehensive code quality dashboard, offering insights into the health of your codebase and identifying potential issues.

Core Features & Use Cases

  • Code Health Check: Computes a weighted composite score from various project tools for code quality and performance.
  • Trend Tracking: Monitors and tracks trends over time to help identify improvements and maintain a high-quality codebase.
  • Use Case: Regularly run this Skill to ensure your codebase remains robust and efficient, catching potential issues early.

Quick Start

Run the 'code health check' command to get a quick overview of your codebase's health.

Frequently Asked Questions about health

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

FAQPage Schema
How do I check my codebase health and track code quality trends over time?

To check codebase health, execute type checkers, linters, test runners, and dead code detectors to compute a weighted composite score. This monitors code quality trends over time by tracking results within your Git repository to identify improvements and catch potential issues early.

What is a composite code health score and how does it evaluate codebase performance?

A composite code health score is a weighted metric calculated by aggregating results from type checkers, linters, test runners, and dead code detectors. It evaluates codebase performance by quantifying code quality into a single trackable indicator for trend analysis.

Do I need a Git repository and pre-configured linters to run a code quality check?

Yes, you need a Git repository and pre-configured project tools including type checkers, linters, test runners, and dead code detectors. The code quality check accesses these dependencies and your Git history to compute scores and track trends.

What's the best way to continuously monitor codebase health during active development?

The best way to continuously monitor codebase health is to regularly run a code health check command during active development. This executes configured project tools to compute a composite score, tracking quality trends to catch potential issues early.