gstack-health

To perform a code health check, you can run a single command that executes type checking, linting, tests, dead code detection, and shell linting, combining the results into a weighted 0-10 composite quality score for your repository.

Yes, you can track code quality trends over time. The health check records snapshots of your composite 0-10 quality score across multiple runs, allowing you to monitor whether your codebase is gradually improving or degrading.

A composite code quality score is a weighted 0-10 metric evaluating repository health. It aggregates results from running type checking, linting, tests, dead code detection, and shell linting into one unified dashboard view.

Yes, the code health dashboard workflow requires executing your wrapped project tools. You must have the necessary type checking, linting, testing, and dead code detection tools already configured in your repository environment.

The best way to automate dead code detection and shell linting alongside tests is using a single automated health check workflow that runs all these checks together and interprets the results into a unified quality score.

Using a single command for code quality checks solves the problem of gradual codebase drift. It provides a repeatable invocation that combines multiple checks into a weighted score and maintains trend history, saving time over running tools separately.