ada-code-quality-report-verification

Sample issues from the report's priority lists, navigate to each claimed file:line, read the actual code, and re-run cited tools like dotnet format or grep counts. Classify each issue as confirmed, partially correct, or false positive with concrete evidence.

Independently count files and lines with find and wc -l excluding obj/ directories, sum the report's own subdirectory breakdowns to check internal consistency, and grep test files to verify coverage claims. Compare each actual value against the reported value.

Use report verification only when a quality report already exists and you need to validate its claims. To generate a new report from scratch, use a code quality analysis skill instead; verification never creates reports.

Yes, Mode C performs fail-closed reviews: it reads SRS/design acceptance criteria first, inspects changed source and focused tests, runs test slices and build gates, and returns a compact passed:true/false verdict with evidence.

Reports frequently miss aggregated test files that contain multiple test classes, or exclude interfaces and DTOs from class counts. Always grep test files for class references rather than trusting the report's coverage table.