| name | sonarqube-workflow |
| description | Fix SonarQube and SonarLint issues using the user-sonarqube MCP server together with IDE Problems/Linter diagnostics. Use when the user mentions SonarQube, SonarLint, quality gates, rule keys (e.g. S3776, S5852), code smells, cognitive complexity, security hotspots, or asks to clear Sonar errors in Problems. |
SonarQube workflow (MCP + IDE)
This repo uses SonarQube connected mode. Project key (do not guess):
# sonar-project.properties
sonar.projectKey=alias8818_enoch-agentic-research-system_6ab334f2-c45e-42db-87ce-a99310229989
Full workflow, MCP tool catalog, and fix loop: use the personal skill at ~/.cursor/skills/sonarqube-workflow/SKILL.md (same content). Agents without that path should follow .cursor/rules/sonarqube_mcp_instructions.mdc plus the steps below.
Cognitive complexity: production python:S3776 / typescript:S3776 threshold 15 per function (see docs/sonarqube-cognitive-complexity.md, .vscode/settings.json, sonar-project.properties).
Quick loop
ReadLints on files you will edit (Problems panel = source of truth for what the user sees).show_rule (user-sonarqube MCP) for the rule key (e.g. python:S3776, typescript:S3776).search_sonar_issues_in_projects optional — open issues on same file/rule; not for instant post-fix verification.- Fix with minimal diff (extract helpers for S3776 / nested ternaries).
analyze_code_snippet with projectKey above, full fileContent, correct language + scope (TEST for tests/**, *.test.ts, e2e/**).ReadLints again until ERRORs on touched lines are gone.- Run targeted tests; CI scan is authoritative on the server.
MCP access
- Server:
user-sonarqube
- Read schemas:
mcps/user-sonarqube/tools/*.json (or Cursor MCP descriptors) before CallMcpTool.
- Supplementary rule file:
.cursor/rules/sonarqube_mcp_instructions.mdc
