sonarqube
Skill1 starsChanged 15 days agoApache-2.0View on GitHub
Fetch and fix SonarQube code quality issues, coverage metrics, security hotspots, and quality gate status. Use when reviewing SonarQube findings for a project or pull request, checking code coverage, investigating security hotspots, verifying quality gate pass/fail, or searching for SonarQube projects.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- zhubby/skillstheir own version, first seen Nov 8, 2026
- Rahlir/clanker-stufftheir own version, first seen Nov 1, 2026
- DougTrajano/pydantic-ai-skillstheir own version, first seen Oct 30, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- DougTrajano/pydantic-ai-skills★ 381same name
- G1Joshi/Agent-Skills★ 15same name
- zhubby/skills★ 6same name
- Rahlir/clanker-stuff★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-chatSkill
- argocdSkill
- code-reviewSkill
- commitSkill
- dependency-trackSkill
- financeSkill
- handoffSkill
- java-21-to-25-migrationSkill
- jenkinsSkill
- jiraSkill
- perplexitySkill
- pr-readySkill
- researchSkill
- shipSkill
- skanetrafikenSkill
- tddSkill
- to-tasksSkill
- verifySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Run ./setup.sh from the repo root (recommended), or create config files manually:
- Distinctive: line 104
Read references/common-rules.md for fix patterns for frequently triggered rules (S3457 logging concatenation, S2629 conditional invocation, …
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SonarQube
Interact with SonarQube to fetch code quality issues, coverage, and quality gate status.
Configuration
Run ./setup.sh from the repo root (recommended), or create config files manually:
mkdir -p ~/.boring/sonarqube
echo 'https://your-sonarqube.example.com' > ~/.boring/sonarqube/url
echo 'your-token' > ~/.boring/sonarqube/token
chmod 600 ~/.boring/sonarqube/tokenFor bearer auth (instead of default token-as-login), also create:
echo 'bearer' > ~/.boring/sonarqube/auth_methodGenerate token: User → My Account → Security → Generate Tokens.
Scripts
Fetch issues
scripts/sonarqube-issues.sh <project-key> [pr-number] \
[--status OPEN,CONFIRMED] [--severity CRITICAL,BLOCKER] \
[--type BUG] [--branch main] [--limit 100]Coverage metrics
scripts/sonarqube-coverage.sh <project-key> [pr-number] [--branch main]For PRs, returns new code coverage. For branches/projects, returns overall coverage.
Security hotspots
scripts/sonarqube-hotspots.sh <project-key> [--pr N] [--branch main] [--status TO_REVIEW]Quality gate status
scripts/sonarqube-quality-gate.sh <project-key> [--pr N] [--branch main]Exits 0 if gate passes, 1 if it fails.
List/search projects
scripts/sonarqube-projects.sh [search-query] [--limit 50]Transition an issue
scripts/sonarqube-transition.sh <issue-key> <transition> [--comment "text"]Transitions: confirm, unconfirm, reopen, resolve, falsepositive, wontfix, accept
Mark issues as false positive, resolved, or won't fix. Optionally attach a comment explaining why.
Raw API
scripts/sonarqube-api.sh <endpoint> [curl-options...]Workflow for fixing issues
S=scripts
# 1. Fetch issues for a PR
$S/sonarqube-issues.sh my-service 327
# 2. Check quality gate
$S/sonarqube-quality-gate.sh my-service --pr 327
# 3. Check coverage
$S/sonarqube-coverage.sh my-service 327
# 4. Check security hotspots
$S/sonarqube-hotspots.sh my-service --pr 327
# 5. Fix issues, verify compilation, commitCommon Java rules and fixes
Read references/common-rules.md for fix patterns for frequently triggered rules (S3457 logging concatenation, S2629 conditional invocation, S1128 unused imports, S5786 JUnit modifiers, etc.).
API reference
Issue search: GET /api/issues/search?componentKeys=KEY&pullRequest=N&issueStatuses=OPEN&severities=CRITICAL&types=BUG&ps=100
Measures: GET /api/measures/component?component=KEY&pullRequest=N&metricKeys=new_coverage,new_line_coverage
Quality gate: GET /api/qualitygates/project_status?projectKey=KEY&pullRequest=N
Hotspots: GET /api/hotspots/search?projectKey=KEY&status=TO_REVIEW
Dashboard URL: <SONARQUBE_URL>/dashboard?id=PROJECT_KEY&pullRequest=PR_NUMBER
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.