Compute a weighted code quality score and dashboard from linter, type checker, and dead code checks.
npx skills add https://github.com/moogieon/kadera --skill health-moogieon
Please help me install this Agent Skill. Skill: health Source: https://github.com/moogieon/kadera/tree/main/.claude/skills/gstack/health Command: npx skills add https://github.com/moogieon/kadera --skill health-moogieon
The health skill provides an overview of your codebase's quality and health status, allowing you to identify and address issues early.
Run 'code health check' to evaluate your codebase's quality.
High-intent search queries and answers about installing and using this skill.
Run a code health check to evaluate your codebase quality by computing a weighted composite score between 0 and 10. The check uses linters, type checkers, and dead code detectors to identify issues early and provide a comprehensive overview of codebase health.
A code quality dashboard tracks codebase health trends over time by aggregating results from linters and type checkers into a weighted composite score. It visualizes quality improvements or regressions, allowing developers to make informed decisions about codebase management.
Yes, you can use linters and type checkers for continuous integration code quality management by running regular health checks. The process computes a 0-10 composite score, detecting dead code and type errors to maintain quality standards within your development environment.
Yes, you need Bash, Grep, Read, Write, Edit, Glob, and AskUserQuestion to perform a codebase health check. These dependencies are required to execute the scripts that run linters, type checkers, and dead code detectors for evaluating code quality.
The best way to identify dead code and quality regressions is to regularly invoke a code health check. This calculates a composite quality score using dead code detectors and linters, tracking the results on a dashboard to quickly spot negative trends.
Your codebase quality score changes between continuous integration runs because the composite score is dynamically calculated using linters, type checkers, and dead code detectors. Any new code commits that introduce errors or remove dead code will impact the weighted result.
cheng80Aggregate type checks, linters, tests, and dead code into a 0-10 health score.
SoSoBurnerAggregate type checker, linter, test runner, and dead code scores into a composite quality score.
SandroBeatzRun ESLint and TypeScript type checking on a codebase.
CodySwannGTRetrieve detailed SonarQube quality gate failure reasons for pull requests.
