gsd-audit-fix

Automated audit-to-fix pipelines classify findings as auto-fixable or manual-only, apply deterministic fixes with test verification, and commit atomically. This integrates directly into continuous integration workflows and local development to progressively improve code quality.

Classifying code quality findings involves evaluating each issue against configurable severity thresholds to determine if it is auto-fixable or manual-only. A dry-run mode can be used to evaluate classification results before any actual code modifications or atomic commits are made.

Yes, dry-run classification mode allows you to evaluate auto-fixable findings without applying changes. You can also configure maximum fixes and severity thresholds to strictly control the scope of automated remediation and test verification during execution.

Automated fixes ensure stability by applying deterministic execution alongside mandatory test verification. Fixes are only committed atomically if the tests pass, ensuring that the auto-fixable changes do not break existing functionality.

Yes, the autonomous audit pipeline is designed for both continuous integration workflows and local development. It reduces manual triage by classifying findings and applying fixes directly to your repository, satisfying requirements for deterministic execution and test verification.

Automated fixes are limited to issues classified as auto-fixable; manual-only findings require human intervention. Additionally, configurable maximum fixes and severity thresholds cap the remediation scope, meaning large-scale issues may need multiple pipeline runs.