sonarqube-analysis

Identify dead code, integration gaps, and quality issues via SonarQube MCP.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matt-metivier/zk-hub --skill sonarqube-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sonarqube-analysis
Source: https://github.com/matt-metivier/zk-hub/tree/main/skills/general/tools/sonarqube-analysis
Command: npx skills add https://github.com/matt-metivier/zk-hub --skill sonarqube-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dead code, integration gaps, and quality issues bog down software projects; this skill provides structured SonarQube MCP-driven analysis to surface actionable improvements.

Core Features & Use Cases

  • Primary audit tools: search_issues, get_component_measures, search_duplicated_files, search_files_by_coverage
  • Deep-dive capabilities: get_file_coverage_details, analyze_file_list, analyze_code_snippet, search_security_hotspots, show_rule
  • Project health: project_status, search_my_projects
  • Use cases: identify dead code, uncover untested paths, measure project health to guide refactoring and releases

Quick Start

Run a SonarQube MCP audit on your project to identify dead code, gaps, and quality issues.

Frequently Asked Questions about sonarqube-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify dead code and quality issues using SonarQube?

SonarQube static analysis identifies dead code and quality issues by running an MCP-driven audit that surfaces actionable improvements using tools like search_issues and search_duplicated_files to analyze your codebase.

Can I measure project health and code coverage details in a self-hosted SonarQube setup?

Yes, you can measure project health in a self-hosted SonarQube setup by using project_status and get_file_coverage_details tools to evaluate dashboards and guide refactoring efforts.

Do I need a self-hosted SonarQube MCP setup to audit codebases?

Yes, a self-hosted SonarQube MCP setup is required to audit codebases, as this approach exposes primary audit and deep-dive tooling like search_security_hotspots to analyze code snippets and untested paths.

What's the best way to uncover untested paths and integration gaps in software projects?

The best way to uncover untested paths and integration gaps is to perform static analysis using SonarQube tools like search_files_by_coverage and analyze_file_list to guide quality improvements and releases.

How does SonarQube static analysis report security hotspots?

SonarQube static analysis reports security hotspots by using the search_security_hotspots tool to deep-dive into specific code components, allowing you to analyze snippets and review applicable rules.