health

Orchestrate code quality tools into a composite 0-10 score with trend tracking.

3|14|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/cegit27/moodle-proctor --skill health-cegit27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/cegit27/moodle-proctor/tree/main/.claude/skills/gstack/health
Command: npx skills add https://github.com/cegit27/moodle-proctor --skill health-cegit27

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the need to manually run scattered code quality tools and interpret inconsistent results. It gives you a single 0-10 score and trend history so you can see if quality is improving or slipping.

Core Features & Use Cases

  • Composite Scoring: Runs type checkers, linters, test runners, dead code detectors, and shell linters, then computes a weighted 0-10 score.
  • Trend Tracking: Compares current scores against historical data to show whether code health is improving or degrading over time.
  • Use Case: Before a release, run this Skill to get a single number that tells you if the codebase is healthy enough to ship, and whether quality has improved since last week.

Quick Start

Use the health skill to run all available code quality checks and show the current composite score and trend.

Frequently Asked Questions about health

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

FAQPage Schema
How do I get a single code quality score from multiple linters and test runners?

You can get a single composite code quality score by orchestrating type checkers, linters, test runners, and dead code detectors into a weighted 0-10 metric. This eliminates the need to manually run scattered tools and interpret inconsistent results.

Can I track code health trends over time for my TypeScript and Python projects?

Yes, you can track code health trends by comparing current composite scores against historical data. This trend tracking identifies whether your TypeScript, JavaScript, and Python codebase quality is improving or degrading over time.

What is the best way to automate a pre-release code health check across different languages?

Automating a pre-release code health check involves running type checkers, linters, test runners, and dead code detectors across TypeScript, JavaScript, Python, and shell scripts. This produces a single 0-10 quality score to determine if your codebase is ready to ship.

Do I need to configure project-specific tooling before running a dead code and type checking health check?

Yes, you need project-specific tooling configuration before running a code health check. The composite scoring system orchestrates your existing type checkers, linters, and dead code detectors based on these predefined project configurations.

How does combining shell linters and dead code detectors improve overall codebase quality tracking?

Combining shell linters and dead code detectors with type checkers and test runners provides a comprehensive weighted 0-10 score. This unified approach improves quality tracking by revealing quality regressions across all supported codebases.

When should I use an automated composite quality score instead of running individual checks?

You should use an automated composite quality score when you need a quick release gate or historical trend analysis. It replaces the friction of manually running and interpreting scattered individual type checkers, linters, and test runners.