skills.rest
adityasingh2400
adityasingh2400COMMUNITY
Explore all skills by this author →
Website𝕏@NoeticPraxisGitHub

health

Compute a 0-10 codebase health score from type checking, linting, tests, dead code detection, and shell lint.

2|Updated Apr 4, 2026
Search Tags:#metrics#dashboard#code-quality#health#lint#ci#trend
One-click install
npx skills add https://github.com/adityasingh2400/SwarmSell --skill health-adityasingh2400
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: health
Source: https://github.com/adityasingh2400/SwarmSell/tree/main/.claude/skills/health
Command: npx skills add https://github.com/adityasingh2400/SwarmSell --skill health-adityasingh2400

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams spend excessive time synthesizing results from disparate quality tools. This skill unifies type checking, linting, tests, dead code detection, and shell lint into a single health dashboard and score.

Core Features & Use Cases

  • Unified health score: weighted 0-10 score across tools, with trend tracking.
  • Tool integration: coordinates type check, lint, test runner, dead code detector, and shell linter.
  • CI/PR health monitoring: reuse in CI to surface health metrics over time and detect regressions.

Quick Start

Run the health skill against your repository to generate a health dashboard and trend data.

Frequently Asked Questions about health

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

FAQPage Schema
How do I calculate a single codebase health score from multiple quality tools?▼

To calculate a codebase health score, you orchestrate type checking, linting, tests, dead code detection, and shell lint to produce a weighted 0-10 score. This unified dashboard synthesizes disparate tool outputs into a single quantifiable metric.

What is codebase health monitoring and how does trend tracking work?▼

Codebase health monitoring aggregates quality metrics over time to detect regressions. Trend tracking works by recording the weighted 0-10 score and per-tool results from each run, allowing you to visualize project health across CI pipelines and historical data.

How do I integrate linting and test results into CI pipelines for PR reviews?▼

You integrate linting and test results into CI pipelines for PR reviews by running a health skill against your repository. This exposes a weighted 0-10 score, trend data, and per-tool insights directly within the CI workflow to surface regressions.

Do I need pre-existing tooling outputs to generate a code quality dashboard?▼

Yes, you need access to the project's tooling outputs to generate a code quality dashboard. The skill requires pre-existing results from type checking, linting, tests, dead code detection, and shell lint to compute the weighted score and trend data.

What's the best way to unify dead code detection and type checking metrics?▼

The best way to unify dead code detection and type checking metrics is using a single dashboard that coordinates these tools. It applies a weighted score across all integrated tools, providing both per-tool insights and a combined 0-10 health rating.

Related Skills

Explore More Software Engineering Skills→
agwacomagwacom

health

Aggregate type checking, linting, tests, dead code, and shell lint into a 0-10 health score.

Official
Intermediate
howdeployhowdeploy
15

health

Aggregate type checker, linter, test, and dead code results into a 0-10 health score.

Community
Advanced
KrismithReddy12KrismithReddy12

health

Calculate a weighted 0-10 code quality score from linters and test runners.

Community
Advanced
23000311472300031147

health

Aggregate code quality metrics into a weighted 0-10 health score dashboard.

Community
Intermediate