codescene-oss/codescene-code-health
Use CodeScene Code Health analysis to safeguard AI-generated code, prioritize technical debt, and guide maintainable refactoring.
Use when the user wants to view, set, or troubleshoot CodeHealth MCP configuration such as OAuth login, access tokens, account IDs, on-prem URLs, default projects, or SSL certificates.
Use when a user asks what Code Health means, how to interpret scores, or why Code Health matters in daily development.
Use when refactoring unhealthy code and needing Code Health findings to choose small safe steps and verify improvement.
Use when installing the CodeHealth MCP Server binary or package, registering it in an AI assistant, or copying agent guidance files into a repository.
Use when a user asks for ROI, stakeholder justification, delivery impact, or defect-risk reduction from improving Code Health in a file.
Use when users with a CodeScene instance ask what to improve first across a project, which hotspots matter most, or how to rank refactoring candidates.
Use when a user asks what to test first based on CodeScene findings, especially for high-risk hotspots or pull-request change sets.
Use when choosing reviewers, domain experts, or likely owners for a file or directory from CodeScene project data.
Use when AI-generated or AI-modified changes need a Code Health gate before commit, handoff, or pull request.