bug-scrub

Aggregating project health signals involves running a read-only diagnostic that collects findings from testing, linting, type checking, and security scans to produce a unified, prioritized markdown and JSON report. This process helps teams identify critical issues across the codebase without manually reviewing each tool's output separately.

A code health diagnostic is a read-only process that detects and aggregates signals from testing, linting, security scans, and code markers to provide a unified view of project status. You need to run one when you want to prioritize remediation before accumulated issues grow into larger problems.

Yes, automated diagnostic reports can be used for automated fixes because the diagnostic process generates both markdown and JSON outputs. The JSON format is specifically structured to be fed into fixing tools to apply the prioritized remediations automatically.

No, the project health diagnostic does not modify your source files during analysis. The process runs Python scripts that parse tool outputs and generate markdown and JSON reports in a strictly read-only manner, ensuring your codebase remains untouched while surfacing health signals.

The best way to prioritize deferred issues and architecture diagnostics is to use a reporting tool that ranks findings by severity and age, groups nearby issues, and generates actionable recommendations. This provides a prioritized list of tasks based on aggregated health signals.