health-check

You assess .NET codebase health by generating an A–F report card across eight dimensions: build status, code quality, architecture, test coverage, dead code, API surface, security, and documentation. The health check uses MCP-assisted analysis and .NET CLI outputs to provide dimension scores with supporting data points.

Evaluating technical debt before a release is best done by running a health check to generate an A–F project health report. This grades eight dimensions like dead code and security posture, providing prioritized remediation recommendations and targeted areas to update.

Yes, you can use MCP tools to check .NET architecture and security posture. The health check skill uses MCP-assisted analysis and security scanning outputs to produce evidence-backed findings and letter grades for your repository's architecture and security dimensions.

Track code quality improvements over time in a .NET project by comparing previous and current health reports. The health check supports trend-friendly reporting, allowing you to compare A–F grades across dimensions like test coverage and code quality to validate post-refactor improvements.

The .NET health check relies on .NET CLI and security scanning outputs to gather evidence for its grading. It uses these outputs alongside MCP tooling to evaluate the security posture dimension, meaning your environment needs to provide these standard .NET scanning capabilities.