Individual skill
sonarqube-ai-slop-gate
Corrects the wrong defaults a model has when standing up self-hosted SonarQube Server as a continuous gate on AI-generated code, verified against docs.sonarsource.com in July 2026 (Server 2026.3, LTA 2026.1). Use when configuring SonarQube, designing a quality gate, or wiring a scan step into CI for AI-assisted work. Covers the setups that run green while measuring almost nothing — the fudge factor skips duplication and coverage conditions below 20 new lines and is on by default; duplication is never measured on test code; no `new_cognitive_complexity` metric exists to gate on; `sonar.host.url` now defaults to sonarcloud.io rather than localhost; a shallow clone degrades new-code attribution to timestamps. Also covers AI Code Assurance — the project flag, gate qualification, the deprecated Copilot autodetection — and that Community Build cannot analyze pull requests at all. NOT for SonarQube Cloud, IDE connected mode, or authoring custom analyzer rules.
skills/.experimental/sonarqube-ai-slop-gate/SKILL.md
Source commit cf93c57cac89d6fc3e4194686000411567f5caf3
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 221
- Repository last updated
- Aug 15, 2026
- License
- MIT
Observed agent integration: codex
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
AGENTS.mddoc · 11,461 bytesSKILL.mdcore · 10,053 bytesassets/templates/_template.mddoc · 2,258 bytesmetadata.jsonasset · 5,610 bytesreferences/_sections.mddoc · 3,452 bytesreferences/aica-do-not-rely-on-autodetection.mddoc · 2,936 bytesreferences/aica-flag-projects-through-the-api.mddoc · 3,037 bytesreferences/aica-qualify-the-gate-explicitly.mddoc · 3,433 bytesreferences/aica-the-builtin-ai-gate-is-lenient.mddoc · 4,442 bytesreferences/aica-use-the-agentic-profile.mddoc · 2,962 bytesreferences/blind-fudge-factor-skips-small-changes.mddoc · 3,345 bytesreferences/blind-java-duplication-threshold-is-fixed.mddoc · 2,853 bytesreferences/blind-no-new-code-complexity-metric.mddoc · 3,037 bytesreferences/blind-pull-requests-hide-file-level-issues.mddoc · 2,778 bytesreferences/blind-suppression-comments-turn-the-gate-green.mddoc · 3,189 bytesreferences/blind-test-code-escapes-duplication.mddoc · 2,986 bytesreferences/newcode-pick-the-definition-deliberately.mddoc · 2,991 bytesreferences/newcode-shallow-clones-break-blame.mddoc · 3,177 bytesreferences/ops-persist-data-and-skip-h2.mddoc · 3,337 bytesreferences/ops-set-host-limits-before-first-boot.mddoc · 2,405 bytesreferences/plat-ai-features-are-edition-gated.mddoc · 3,043 bytesreferences/plat-community-build-cannot-see-pull-requests.mddoc · 2,867 bytesreferences/plat-versions-are-calendar-based.mddoc · 2,847 bytesreferences/scan-declare-test-sources.mddoc · 2,864 bytesreferences/scan-exclude-narrowly.mddoc · 3,308 bytesreferences/scan-host-url-defaults-to-the-cloud.mddoc · 2,337 bytesreferences/scan-import-coverage-reports.mddoc · 3,108 bytesreferences/scan-name-the-branch.mddoc · 2,793 bytesreferences/scan-use-project-analysis-tokens.mddoc · 3,144 bytesreferences/scan-wait-for-the-quality-gate.mddoc · 3,032 bytes
Read excerpt
# SonarQube AI Slop Gate
The decisions self-hosted SonarQube forces when you use it to gate AI-generated code, and how to settle them. Every rule names the wrong default it corrects; there is no rule for what the model already gets right.
**Pinned to a date, not a version.** SonarQube ships a release every two months, so every claim here was verified against docs.sonarsource.com in **July 2026**, against **SonarQube Server 2026.3** (current LTA **2026.1**). 2026.4 had shipped at the time of writing but the documentation still defaulted to 2026.3, so that is what these rules describe — `plat-versions-are-calendar-based` covers the release train itself. Re-verify anything version-shaped before trusting it, and read docs from the **unversioned** path (`/latest/<page>` does not resolve); appending `.md` to any docs URL returns its markdown source.
**The failure this skill exists to prevent** is a gate that passes everything. A SonarQube setup assembled from 2024-vintage knowledge will analyze the wrong branch, upload to the wrong server, exit green on a red gate, and skip the duplication and coverage conditions entirely on the small commits that AI-assisted work produces most of. None of those failures announce themselves; the dashboard looks healthy throughout.
## When to Apply
Use this skill when:
- Standing up self-hosted SonarQube Server, or reviewing an existing instance, with the goal of catching AI-generated defects continuously rather than reporting on them after the fact
- Designing or tightening a quality gate — especially deciding what to measure on new code versus overall code, and discovering which conditions are silently not evaluated