A score alone would be a scold; what makes this usable is the pairing — the review says what specifically degraded, the pre-commit safeguard catches it before it is someone else's problem, and the business case tool exists for when you have to justify the cleanup. The rules configuration matters too: thresholds are per language and adjustable, so the metric can be tuned to the codebase instead of argued with.
CodeScene's Code Health analysis running locally as tools: single-file scores and reviews, branch-level change-set analysis, a pre-commit safeguard, and the technical-debt data from your CodeScene project.
- A Code Health score for a source file on a 10.0 scale, and a full review explaining what pulled it down
- Branch-level review of every file that differs from a base ref, so the analysis matches the diff under discussion
- A pre-commit safeguard that reviews modified and staged files and reports degradations before the commit lands
- The metric itself explained, for the model and for the human reading its output
- A business case generator that argues a refactoring in terms of the empirical productivity data behind Code Health
- Project-level technical debt: hotspots and goals for the whole project or for a specific file
- Ownership lookup for a path, which turns an impacted file into a likely reviewer
- Rules tuned in a code-health-rules.json: list the default thresholds for a language, enable or disable a rule, set a threshold, and validate the file
- Embedded agent skills that can be listed, inspected by manifest, and downloaded individually or all at once into your own pipeline
- Setup help — configuration read and written, and an installation check that diagnoses a broken setup
A CodeScene account: sign in through the built-in OAuth flow, or set CS_ACCESS_TOKEN and skip it. Runs locally against your working copy rather than uploading it. Published on npm as @codescene/codehealth-mcp, with Docker, Homebrew and prebuilt executable installs documented for macOS, Linux and Windows. Project-level hotspot and goal tools need a CodeScene project selected. Which agent guidance file you copy into the repository depends on your licence.
One command plus a key — npx @codescene/codehealth-mcp, then supply credentials