health-audit

Name: health-audit
Availability: InStock
Author: sebdysart

Analyze multiple repositories to score test coverage, code quality, dead code, and TODO burden.

Updated Mar 8, 2026

Search Tags:#code quality #technical debt #codebase analysis #risk assessment #recommendations #health audit

Ready to run

npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill health-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: health-audit
Source: https://github.com/Sebdysart/omni-link-hustlexp/tree/main/skills/health-audit
Command: npx skills add https://github.com/Sebdysart/omni-link-hustlexp --skill health-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a comprehensive assessment of your codebase's health, identifying risks and offering actionable recommendations to improve quality and maintainability.

Core Features & Use Cases

Ecosystem Health Scoring: Generates overall and per-repo scores based on test coverage, code quality, dead code, and TODOs.
Risk Zone Identification: Pinpoints areas with low scores or specific issues like high dead code ratios or compilation errors.
Actionable Recommendations: Provides prioritized steps for remediation, tailored to identified risks.
Use Case: Before starting a major refactor, run /health to understand the current state of your codebase and prioritize areas needing the most attention.

Quick Start

Run the health audit by typing /health.

Frequently Asked Questions about health-audit

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

FAQPage Schema

How do I assess technical debt and code quality across multiple repositories?▼

An ecosystem health audit assesses technical debt across multiple repositories by calculating scores based on test coverage, code quality, dead code, and TODOs, identifying risk zones and providing prioritized recommendations.

What is ecosystem health scoring and how does it evaluate a codebase?▼

Ecosystem health scoring evaluates a codebase by generating overall and per-repository scores derived from test coverage, code quality metrics, dead code ratios, and TODO burden to highlight specific areas needing remediation.

How do I identify risk zones and dead code before starting a major refactor?▼

Identify risk zones before a refactor by running a health audit that flags areas with low scores, high dead code ratios, compilation errors, contract mismatches, and convention divergence across your repositories.

Can I perform a deep dive into individual repository health during an ecosystem audit?▼

Yes, you can perform a deep dive into individual repository health during an ecosystem audit by dispatching a dedicated repo-analyst agent to investigate specific low-scoring areas and compilation issues.

Does the health audit detect ecosystem-level concerns like convention divergence?▼

Yes, the health audit detects ecosystem-level concerns by flagging convention divergence and contract mismatches between repositories, alongside calculating individual repository scores for test coverage and dead code.

What are the limitations of using automated codebase analysis for risk assessment?▼

Automated codebase analysis for risk assessment is limited to quantifiable metrics like test coverage, dead code, and TODOs, meaning it may not capture subjective architectural flaws or nuanced business logic risks without manual review.