code-quality

Use this agent for multi-step SonarQube workflows that combine multiple skills: full project quality audits, batch issue fixing, RED/GREEN verification cycles, or PR quality reviews. This agent orchestrates sonar-status, sonar-issues, sonar-fix, sonar-verify, sonar-triage, and sonar-rule into coherent multi-step flows. Triggers: "quality audit", "batch fix sonar", "fix all issues", "PR quality review", "sonar workflow".

Use when inspecting the local SonarQube infrastructure: which IDE embedded servers are running, which ports they own, and which MCP Docker containers are active. Also use when the user asks "what's listening on the sonar ports?", "which IDE is my MCP connected to?", or wants to check for port mismatches or orphaned containers. Triggers: "sonar environment", "sonar ports", "sonar-env", "sonar containers", "mcp containers", "port mismatch", "what's running", "check sonar infra", "sonar docker".

Use when the user wants to fix a SonarQube issue, resolve a code smell, or address a flagged violation. Also use when the user says "fix this issue", "resolve the ternary", or "clean up sonar findings". Triggers: "fix sonar", "fix issue", "resolve code smell", "fix violation", "sonar fix", "clean up issue", "address finding". Not for: triaging false positives (use sonar-triage), browsing issues without fixing (use sonar-issues).

Use when browsing, searching, or listing SonarQube issues for a project or PR. Also use when the user asks "what issues are there?", "show me the code smells", or wants to see issues by severity. Triggers: "sonar issues", "code smells", "show issues", "list issues", "what issues", "browse issues", "sonar findings".

Use when the user asks about a SonarQube rule, wants to understand why code was flagged, or needs compliant/noncompliant examples. Also use when seeing rule IDs like "S3358" or "typescript:S1135". Triggers: "explain rule", "what is S3358", "sonar rule", "why was this flagged", "show rule", "rule details", "noncompliant example".

Use when setting up SonarQube MCP integration, diagnosing connectivity issues, or checking which code-quality skills are functional. Also use when the user asks "is SonarQube working?", "set up sonar", or wants to enable IDE-connected mode. Triggers: "sonar setup", "configure sonarqube", "sonar not working", "mcp connection", "ide mode", "analyze_file_list", "sonar connectivity".