Aggregate type checker, linter, test, and shell check scores into a 0-10 repository health view.
npx skills add https://github.com/ClyptAI/Clypt-Backend --skill health-clyptai
Please help me install this Agent Skill. Skill: health Source: https://github.com/ClyptAI/Clypt-Backend/tree/main/.agents/skills/gstack/health Command: npx skills add https://github.com/ClyptAI/Clypt-Backend --skill health-clyptai
Code quality varies across projects and teams. A single dashboard that aggregates the results from multiple tools helps teams understand the health of their codebase at a glance.
Run the health skill to generate a live dashboard of your repository's code health.
High-intent search queries and answers about installing and using this skill.
To aggregate code quality metrics into a single dashboard, this Skill wraps your existing type checker, linter, test runner, dead code detector, and shell linter into a unified health view. It computes a weighted 0-10 score to track repository health trends over time.
A weighted code health score is a 0-10 metric calculated by aggregating results from type checkers, linters, tests, and shell checks. It monitors regression risks by tracking this score over time as a time-series view, revealing improvements or degradations in your active codebase.
Yes, you can use this code health dashboard to monitor CI pipelines and PR reviews. It supports health checks across local development and CI pipelines by integrating various quality tools to guide targeted code improvements during pull requests.
You track code quality trends over time by running this Skill on an active codebase. It integrates your type checker, linter, test runner, dead code detector, and shell linter to produce a time-series health view, surfacing trend changes and regression risks.
Yes, you need a linter and type checker to generate a repository health score. The Skill requires integrating a type checker, linter, test runner, dead code detector, and shell linter to apply its weighted 0-10 scoring model effectively.
The best way to surface dead code and linting issues is by wrapping your existing dead code detector and shell linter into this unified health view. It aggregates their outputs to reveal overall repository health and surface regression risks at a glance.
robertzengcnAggregate code quality metrics from multiple tools into a weighted 0-10 composite score.
jonkikyAggregate type checking, linting, tests, and dead code detection into a weighted 0-10 health score.
stayconnectquickAggregate code quality metrics into a 0-10 health score with trends.
chriswesttAggregate quality tool results into a weighted 0-10 health score.
