fix-sonarqube_skill

Overview

This skill integrates SonarQube via a remote MCP (Model Context Protocol) server to inspect and fix Java code quality issues. It requires no local setup—use natural language to query issues, analyze code snippets, and check quality gates. The MCP server is preconfigured for supported IDEs and exposes tools for common SonarQube workflows.

How this skill works

The skill queries a remote SonarQube MCP endpoint to list projects, fetch issues, retrieve rule documentation, and evaluate quality gates. You can send plain-language requests like finding high-severity issues, asking for rule explanations, or submitting code snippets for analysis. Results include issue lists, rule details, remediation guidance, and quality gate status.

When to use it

• When you need to find and fix SonarQube issues in Java projects
• To check quality gate status for a service or project
• When prioritizing remediation by severity or rule
• To get explanations for specific SonarQube rules
• When you want to analyze code snippets for SonarQube violations

Best practices

• Ask for issues scoped by project and severity (e.g., BLOCKER, CRITICAL) to focus remediation
• Request rule details before changing code to ensure fixes align with rule intent
• Use code snippet analysis for narrow, incremental fixes rather than whole-repo rewrites
• Check quality gate status after fixes to validate improvements
• Integrate queries into your IDE using the provided MCP configuration for faster feedback

Example use cases

• Find all BLOCKER issues in payment-service and list remediation steps
• Show rule java:S1128 (unused imports) and examples of compliant code
• Check the quality gate status for my-service before a release
• Analyze a code snippet and return SonarQube issues with suggested fixes
• List projects I have access to and summarize open CRITICAL issues