skills.rest
denniscalazans
denniscalazansCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sonar-env

Diagnoses SonarQube integration issues by inspecting IDE servers and Docker containers.

3|1|Updated Mar 2, 2026
Search Tags:#troubleshooting#mcp#docker#ide integration#port scanning#sonarqube
One-click install
npx skills add https://github.com/denniscalazans/denniscalazans-plugins --skill sonar-env
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sonar-env
Source: https://github.com/denniscalazans/denniscalazans-plugins/tree/main/plugins/code-quality/skills/sonar-env
Command: npx skills add https://github.com/denniscalazans/denniscalazans-plugins --skill sonar-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps diagnose and understand the local SonarQube setup, identifying potential issues with IDE integrations, MCP container configurations, and port conflicts.

Core Features & Use Cases

  • Identify Running IDE Servers: Detects which IDEs (VS Code, IntelliJ, etc.) have SonarQube embedded servers running and on which ports.
  • List Active MCP Containers: Shows all running mcp/sonarqube Docker containers, their connection ports, and URLs.
  • Detect Mismatches: Flags issues like MCP containers pointing to non-existent IDE ports or multiple containers with the same configuration.
  • Use Case: When code analysis is failing silently, this Skill can reveal if the MCP container is trying to connect to the wrong port or if an IDE server isn't running.

Quick Start

Use the sonar-env skill to scan your local SonarQube infrastructure.

Frequently Asked Questions about sonar-env

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

FAQPage Schema
How do I troubleshoot SonarQube IDE integration when code analysis fails silently?▼

Troubleshoot SonarQube IDE integration by scanning local infrastructure to detect orphaned MCP Docker containers, identify unconnected IDEs, and flag port mismatches causing silent analysis failures.

Why does my SonarQube MCP Docker container fail to connect to my IDE server?▼

Your SonarQube MCP Docker container fails to connect due to port mismatches. Scanning infrastructure identifies if the MCP container points to a non-existent IDE port or if the IDE server is not running.

Do I need lsof and docker installed to diagnose local SonarQube infrastructure?▼

Yes, you need both lsof and docker installed and functional. These dependencies are required to scan running IDE servers and list active MCP Docker containers for SonarQube integration troubleshooting.

How can I find which IDEs have SonarQube embedded servers running locally?▼

Find running SonarQube embedded IDE servers by scanning local infrastructure. This detects active IDEs like VS Code or IntelliJ and reports the specific ports they use for integration.

Can I detect duplicate SonarQube MCP containers with the same configuration?▼

Yes, you can detect duplicate SonarQube MCP containers. Scanning local infrastructure flags configuration issues like multiple mcp/sonarqube Docker containers pointing to the same IDE port.

Related Skills

Explore More Software Engineering Skills→
wesleyosantos91wesleyosantos91
6

local-setup

Validate Docker compose, Floci port 4566, and local configuration readiness.

Community
Basic
saskinosiesaskinosie
39

weaviate-local-setup

Sets up and manages a local Weaviate Docker instance with vectorizers and data persistence via Docker volumes.

Community
Advanced
denniscalazansdenniscalazans
3

sonar-setup

Diagnose SonarQube MCP integration setup and connectivity issues.

Community
Intermediate
yongwoonyongwoon
8

ywc-docker-isolate

Derive deterministic Docker port blocks and project names per Git worktree.

Community
Advanced