SonarQube Auto-Fix

When to Use

• User asks or mentions this skill in English (e.g., "use /sonarqube-autofix", "run sonarqube-autofix").
• O usuário pede ou menciona esta skill em português (ex.: "use /sonarqube-autofix", "execute sonarqube-autofix").

Purpose

Analyze issues reported by SonarQube, regardless of language or framework, classify them by type, and create approved SPEC SDDs that describe the fixes. The actual implementation of each SPEC is delegated to /execute-specs.

The process is:

1. Issue analysis — download and inspect unresolved SonarQube issues.
2. Classification — group issues by type: bug, code smell, or security.
3. SPEC generation — write one SPEC SDD per issue (or per small, related group) using references/spec-sdd-template.md; if the write-specs skill is available, use it to author the SPECs.
4. GitHub issues — open the issues on GitHub, one per generated SPEC (or per related group), so every fix is trackable; if the create-issues skill is available, use it.
5. Hand-off — mark each SPEC as Approved and invoke /execute-specs to implement the fixes.
6. QA hand-off — when all fixes are done, invoke /qa-analyst to re-validate the applied corrections (see Phase 4, step 5).