Branch: refs/heads/sonar-prevent-before-silencing Home: https://github.com/xwiki/xwiki-dev-llm Commit: fc59a7d5c1bf52f94acf00f77cfc30749a7b787d https://github.com/xwiki/xwiki-dev-llm/commit/fc59a7d5c1bf52f94acf00f77cfc30... Author: Vincent Massol <[email protected]> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M xwiki/okf/sonarqube/index.md M xwiki/skills/xwiki-fix-sonarqube-issue/SKILL.md Log Message: ----------- [Misc] Make the Sonar sweep propose prevention before silencing a finding * Retiring a finding (`@SuppressWarnings`, False positive, Accepted) is now the last resort and the developer's call, never the sweep's. * Before proposing it, the skill must work out what would stop the rule firing at all -- refactoring the flagged shape, adding the API the idiom is missing (old one deprecated into `-legacy`), encapsulating the idiom once, or deferring the change with the finding left OPEN -- and present each with its cost and its risk. * A deferred change earns a JIRA issue only when it touches public API; a pure refactoring ships as `[Misc]`. * Separate dropping an issue (too costly, stays OPEN for a later sweep) from retiring it, which the Rules section conflated. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications