Health

Integrate quality tools to monitor codebase health and track trends.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill health-aporto-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Health
Source: https://github.com/aporto-tech/aporto-agent-skills/tree/main/skills/gstack/health
Command: npx skills add https://github.com/aporto-tech/aporto-agent-skills --skill health-aporto-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive view of your codebase's health by integrating various quality tools and tracking trends over time.

Core Features & Use Cases

  • Code Quality Dashboard: Wraps existing project tools for type checking, linting, testing, and dead code detection.
  • Composite Score: Computes a weighted composite score between 0-10 to represent overall code health.
  • Trend Tracking: Tracks and visualizes the health of the codebase over time.
  • Use Case: Use this Skill to quickly assess the health of your codebase and identify areas that need improvement.

Quick Start

Run the Health skill to get a comprehensive report on 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 monitor codebase health and track quality trends over time?

You can monitor codebase health by running a comprehensive health check that integrates type checkers, linters, and test runners. This generates a dashboard with a weighted 0-10 composite score and visualizes quality trends over time to identify areas needing improvement.

What is a composite score for code quality and how is it calculated?

A composite score is a weighted value between 0-10 representing overall codebase health. It is calculated by aggregating results from integrated quality tools, including type checkers, linters, test runners, and dead code detectors, into a single quantifiable metric.

Do I need to configure type checkers and linters before running a code health check?

Yes, you need to have existing project tools like type checkers, linters, test runners, and dead code detectors configured. The health check wraps these existing quality tools to aggregate their results and compute the overall codebase health composite score.

Can I use this code quality dashboard with my existing software development workflows?

Yes, the code quality dashboard applies to software development workflows requiring ongoing assessment. It integrates with your existing project tools to continuously monitor and report on the health of your codebase throughout the development lifecycle.

What's the best way to identify dead code and areas needing improvement in my codebase?

The best way is to run a comprehensive health check that wraps a dead code detector alongside type checkers, linters, and test runners. This generates a dashboard highlighting weak areas and tracks quality trends to pinpoint exactly what needs improvement.

Why does tracking code quality trends help with software development?

Tracking code quality trends helps by providing a historical view of codebase health through a comprehensive dashboard. Visualizing these trends over time allows development teams to quickly assess the impact of changes and identify recurring areas that need improvement.