sonarqube-autofixlisted

# 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-tdd-spec`. 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`. 4. **Hand-off** — mark each SPEC as `Approved` and invoke `/execute-tdd-spec` to implement the fixes. ## ⚙️ Environment Variable Configuration The skill supports multiple SonarQube editions through environment variables. Detection is automatic based on the availability of the variables (in priority order): > **⚠️ IMPORTANT:** For security, NEVER read, print, or inspect the value of environment variables that contain tokens. The most you may know is which variable the token is stored in. Use the variables directly in commands without accessing their contents. ### Available Variables #### For Custom URL (Highest Priority) - `SONARQUBE_CUSTOM_URL`: Base URL of the custom SonarQube - `SON