Borrowing it
Nothing to install: this file belongs to boecht/birre. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/boecht/birre/main/.github/prompts/fix-sonarqube-findings.prompt.mdgit clone --depth 1 https://github.com/boecht/birreWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/boecht/birre/fix-sonarqube-findings)<a href="https://agentmods.dev/commands/boecht/birre/fix-sonarqube-findings"><img src="https://agentmods.dev/badge/commands/boecht/birre/fix-sonarqube-findings/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/boecht/birre/fix-sonarqube-findings"><img src="https://agentmods.dev/badge/commands/boecht/birre/fix-sonarqube-findings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.01217 |
| Opus 5 | $0.00000 | $0.00609 |
| Sonnet 5 | $0.00000 | $0.00243 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
fix-sonarqube-findings scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Objective
Drive the codebase to a state where SonarQube (security / code quality hotspots surfaced via list_potential_security_issues) AND the IDE Problems list report zero outstanding actionable findings for the targeted files. Maintain functional and test integrity while applying minimally invasive, high-quality fixes.
Scope
- Start with files currently showing findings.
- Enumerate ALL findings from BOTH sources:
- Sonar (security & code quality): prefer
sonarsource.sonarlint-vscode/sonarqube_getPotentialSecurityIssuesplussonarsource.sonarlint-vscode/sonarqube_analyzeFilefor full file after every change. Fallback:sonarqube/analyze_code_snippetfor targeted snippet validation;sonarqube/show_rulefor rule metadata. - Problems: use
problems(get_errors) per file.
- Sonar (security & code quality): prefer
- Treat both sources as complementary; merge/normalize into a unified issue list (deduplicate identical root causes).
- Expand scope if fixes introduce new findings elsewhere (iterate until stable zero state).
Issue Categories & Typical Fixes
| Category | Source(s) | Fix Strategy |
|---|---|---|
| Insecure protocol (http→https) | Sonar | Replace with https if endpoint supports it (most public domains). Canonicalize duplicated literals simultaneously. |
| Duplicate string literals | Problems | Introduce a module-level constant (ALL_CAPS) or reuse existing constants; avoid over-abstraction. |
| Other (if discovered) | Both | Apply least intrusive change preserving semantics, with docstring/comment only when intent could be unclear. |
Process
- Planning: Use
todosto outline each issue (security > maintainability priority). - Enumeration: For each candidate file, collect Sonar + Problems findings.
- Normalization: For each finding record: source(s), rule/message, line(s), proposed fix, risk level (security/maintainability).
- Fix Implementation Order: a. Security hotspots (Bugs, Vulnerabilities, other blocking and critical findings). b. Refactors reducing duplication or maintainability warnings.
- Apply edits in cohesive commits (the assistant session groups them; human will commit later). Keep changes minimal; do not introduce new deps.
- Re-run Problems + Sonar listing after each batch:
- If residual issues remain, iterate.
- Run tests (
runTests) focusing on affected unit tests or full suite if low cost. - If a reported issue is a false positive or intentionally retained (rare):
- Verify via rule description (
sonarqube/show_rule). - Only if justified, consider marking accepted (
sonarqube/change_sonar_issue_status), but PREFER code fix—document rationale inline in a concise comment.
- Verify via rule description (
- Finish when both sources return zero actionable findings and tests pass.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 115 lines · 0 tokens per session scan A 969a314f5e49
fix-sonarqube-findings is a command published in the GitHub repository boecht/birre (2 stars, last pushed today), licensed Unlicense. It costs nothing until one of its globs matches a file; then it loads 1,217 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
fix
Universal debugging and fix application with semantic code analysis.
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
gh-issue-use-cypress
Like /gh-issue-use-browser, but pinned to the Cypress MCP — use when your project runs the Cypress MCP for browser automation. Example — /gh-issue-use-cypress "Composer > Save" saving toasts failure but the record persists.