Menú
Inspect SonarQube quality gates, issues, and source using the SonarQube MCP tools.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
| name | sonarqube-ops |
| description | Inspect SonarQube quality gates, issues, and source using the SonarQube MCP tools. |
Use this skill when you need to:
mcp--sonarqube--search_my_sonarqube_projectsmcp--sonarqube--get_project_quality_gate_status with pullRequestmcp--sonarqube--get_project_quality_gate_status with branch (or omit for default)mcp--sonarqube--search_sonar_issues_in_projectsmcp--sonarqube--show_rulemcp--sonarqube--get_raw_source.kilocode/mcp.json). Ensure it is available in your environment before using these tools.mcp--sonarqube--search_my_sonarqube_projects firstanalyze_file_list or toggle_automatic_analysis tools exist, use them per the SonarQube MCP server instructions (disable auto-analysis at task start, re-enable + analyze at task end)Use Beads (bd) with Dolt server backend for multi-repo task tracking.
Use GitHub CLI (gh) and SonarQube MCP tools to fetch PR details, review comments, threads, and quality gate status for the current branch before addressing code review feedback.
Use structured sequential thinking for multi-step debugging, architecture decisions, or ambiguous problem framing.
Retrieve up-to-date third-party library docs via Context7 (resolve-library-id then query-docs) before implementing integrations.
Use Augment context engine codebase-retrieval for semantic code search and architecture understanding before editing or refactoring.