sonar-issues

List SonarQube issues by severity with pagination and filtering.

3|1|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/denniscalazans/denniscalazans-plugins --skill sonar-issues
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sonar-issues
Source: https://github.com/denniscalazans/denniscalazans-plugins/tree/main/plugins/code-quality/skills/sonar-issues
Command: npx skills add https://github.com/denniscalazans/denniscalazans-plugins --skill sonar-issues

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying, reviewing, and understanding code quality issues reported by SonarQube, helping to maintain a high standard of code health.

Core Features & Use Cases

  • Issue Browsing: View SonarQube issues with clear severity filtering and pagination.
  • Code Smells Identification: Easily find and understand code smells within your project.
  • Use Case: When a pull request is opened, use this Skill to quickly list all critical and major issues introduced, allowing for immediate feedback and remediation.

Quick Start

Use the sonar-issues skill to show me all critical and major code smells in the current project.

Frequently Asked Questions about sonar-issues

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

FAQPage Schema
How do I list SonarQube code smells by severity for a specific pull request?

You can list SonarQube code smells by severity for a pull request by using the skill to retrieve and filter issues. It categorizes issues by severity and supports safe pagination for project-wide or pull request-specific analysis.

Can I filter SonarQube issues to show only critical and major vulnerabilities?

Yes, you can filter SonarQube issues to show only critical and major vulnerabilities or code smells. The skill categorizes retrieved issues by severity, allowing you to quickly isolate high-priority code quality problems for remediation.

Do I need a SonarQube API integration to fetch and review code quality issues?

Yes, you need a SonarQube API integration to fetch and review code quality issues. The skill requires integration with SonarQube's API via a subagent to search, fetch, and format the issue data for analysis.

What is the best way to identify and categorize code smells during a code review?

The best way to identify and categorize code smells during a code review is by searching SonarQube issues. This skill fetches and formats issue data, categorizing code smells by severity to streamline code health analysis and feedback.

How does pagination work when retrieving large volumes of SonarQube issues?

Pagination works safely when retrieving large volumes of SonarQube issues by fetching and formatting data through the API subagent. This ensures all code quality issues are listed and categorized by severity without exceeding retrieval limits.