health

Analyze code quality with multiple tools and compute a weighted composite score.

3|Updated Oct 12, 2025
One-click install
npx skills add https://github.com/mostafasudo/warpy --skill health-mostafasudo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/mostafasudo/warpy/tree/main/.codex/skills/gstack/health
Command: npx skills add https://github.com/mostafasudo/warpy --skill health-mostafasudo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a quick overview of the codebase's health, offering a weighted composite score and identifying issues that need attention.

Core Features & Use Cases

  • Composite Score: Computes a 0-10 score that reflects the overall health of the codebase.
  • Code Quality Checks: Wraps type checkers, linters, test runners, and dead code detectors.
  • Trend Tracking: Monitors and tracks code quality trends over time.
  • Use Case: Utilize this Skill during code reviews or periodic health checks to get a quick pulse on the codebase's health.

Quick Start

Perform a health check on your codebase by running the 'code health check' command.

Frequently Asked Questions about health

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

FAQPage Schema
How do I perform a code health check and get a quality score for my project?

To perform a code health check, run the 'code health check' command in your project directory. This computes a weighted composite 0-10 score reflecting overall codebase health by analyzing type checkers, linters, test runners, and dead code detectors.

What does a composite codebase health score measure during a quality assessment?

A composite codebase health score measures overall code quality on a 0-10 scale. It aggregates results from static analysis, type checking, linting, test execution, and dead code detection to identify issues needing attention during code reviews.

Can I track code quality trends over time using static analysis tools?

Yes, you can track code quality trends over time by running periodic health checks. The Skill monitors your codebase by wrapping static analysis, linters, and test runners to compute a historical weighted quality score.

Do I need to configure linters and type checkers before running a codebase analysis?

Yes, you need linters, type checkers, test runners, and dead code detectors configured in your project. The codebase analysis requires access to these existing tools and your source code to compute the weighted composite health score.

What's the best way to identify dead code and quality issues for code reviews?

The best way to identify dead code and quality issues is to run a comprehensive health check. It wraps dead code detectors and linters to analyze your codebase, outputting a 0-10 quality score and highlighting specific issues requiring attention.

Why does my code health score change between different project assessments?

Your code health score changes because it is a weighted composite dynamically calculated from multiple tools. Variations in type checking errors, linting violations, test failures, or dead code volume between assessments will alter the final quality score.