gsd-audit-fix

Automating audit finding fixes involves identifying issues, classifying them as auto-fixable or manual-only, applying fixes, and verifying resolutions with tests. This skill executes that end-to-end workflow using command-line operations.

Classifying audit issues for automated resolution means categorizing findings into auto-fixable and manual-only groups. This skill autonomously performs this classification, applies fixes to the auto-fixable set, and commits changes atomically.

Running an automated audit-to-fix pipeline with test verification requires executing a command specifying the audit source, severity, and max findings, such as `run-audit --source audit-uat --severity medium --max 5`. The pipeline handles execution, classification, fixing, and testing.

Yes, the automated audit fix workflow requires Bash, Grep, Glob, and other command-line tools to execute audit operations, classify findings, apply automated fixes, and perform test verification on your codebase.

Automated code fixes are committed atomically to maintain data integrity. Each resolved audit finding is committed as a single, indivisible unit after passing test verification, preventing partial or broken changes.

You should avoid using an autonomous audit-to-fix pipeline for findings classified as manual-only, as the automation specifically targets and resolves routine auto-fixable issues to reduce manual effort and potential errors.