fleet-scanning-quality

Code-quality scanning before a release involves orchestrating multiple finders to analyze your repository in parallel, deduplicating the results, and synthesizing them into an A-F prioritized markdown report with actionable fixes.

Adversarial verification in code scanning optionally attempts to refute high-severity findings to strengthen confidence, ensuring critical bugs and security regressions identified during repository analysis are accurate before final reporting.

Yes, automated code-quality scanning can be applied when a recent diff touches security-sensitive code. It coordinates parallel finders and variant-analysis across the entire codebase to surface broader related issues.

Variant-analysis improves repository scanning by cross-checking High and Critical findings for related patterns, effectively surfacing broader issues across the codebase that might be missed by individual finders working in isolation.

The best way to deduplicate code-quality findings is to use an orchestrated scanning workflow that coordinates multiple parallel finders, cross-checks results, and synthesizes a deduplicated A-F prioritized markdown report.

No dependencies are required to run orchestrated code-quality scans. The skill operates independently to coordinate parallel finders, perform variant-analysis, and generate a prioritized A-F markdown report.