sonar-verify

Validate SonarQube issue resolutions by cross-referencing server and local analysis.

3|1|Updated Mar 2, 2026

Search Tags:#code quality #ci/cd #debugging #verification #sonarqube #pre-push check

Ready to run

npx skills add https://github.com/denniscalazans/denniscalazans-plugins --skill sonar-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sonar-verify
Source: https://github.com/denniscalazans/denniscalazans-plugins/tree/main/plugins/code-quality/skills/sonar-verify
Command: npx skills add https://github.com/denniscalazans/denniscalazans-plugins --skill sonar-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers ensure their code changes have actually fixed SonarQube issues before pushing to the repository, preventing the reintroduction of known problems and saving review time.

Core Features & Use Cases

Cross-reference Server and Local Issues: Compares issues reported by SonarQube with local analysis results.
Identify Fixed Issues (GREEN): Highlights issues present on the server but not found locally, indicating successful fixes.
Identify Remaining Issues (RED): Shows issues still present both on the server and locally, meaning they need further attention.
Detect New Issues (NEW): Flags issues found locally in changed code that were not reported by the server.
Identify Pre-existing Issues (PRE-EXISTING): Points out issues found locally in unchanged code that the server did not flag.
Use Case: After fixing several SonarQube warnings, run this skill to confirm which ones are truly resolved and which ones were missed, before creating a pull request.

Quick Start

Run the sonar-verify skill to check which SonarQube issues have been fixed locally.

Frequently Asked Questions about sonar-verify

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

FAQPage Schema

How do I verify SonarQube fixes locally before pushing code?▼

To verify SonarQube fixes locally, cross-reference server-reported issues with local analysis results to identify fixed, remaining, and new issues before pushing. This RED/GREEN validation requires IDE-connected mode and Git diff comparisons to confirm resolutions.

What is the best way to check if SonarQube warnings are resolved in my workspace?▼

Checking if SonarQube warnings are resolved involves comparing server issues against local code analysis. This process highlights fixed issues (GREEN), remaining issues (RED), and flags new or pre-existing issues within your workspace.

Do I need IDE-connected mode to run local SonarQube issue validation?▼

Yes, IDE-connected mode is required for local SonarQube issue validation. It enables local analysis and Git diff comparisons, which are necessary to cross-reference server-reported issues with your code changes.

How does local SonarQube analysis detect new issues in changed code?▼

Local SonarQube analysis detects new issues by comparing local analysis results against server-reported issues. It flags issues found locally in changed code that were not previously reported by the SonarQube server.

Can I identify pre-existing SonarQube issues in unchanged code locally?▼

Yes, you can identify pre-existing SonarQube issues in unchanged code locally. The validation process points out issues found locally in unchanged code that the server did not flag, helping isolate baseline problems.