Branch: refs/heads/ci-check-closed-flicker-issues Home: https://github.com/xwiki/xwiki-dev-llm Commit: 03e58f6ed4e2c01df5d546c4a4bba701804f7998 https://github.com/xwiki/xwiki-dev-llm/commit/03e58f6ed4e2c01df5d546c4a4bba7... Author: Vincent Massol <[email protected]> Date: 2026-09-20 (Sun, 20 Sep 2026) Changed paths: M xwiki/okf/processes/release.md M xwiki/scripts/jira-flickers.mjs M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] Say each of these rules once, in the file that owns it Self-review of this PR against the gate it adds: it stated the same thing in several places, and duplicated a policy that already had a home. * Move the "never name the unsupported LTS line in a public artifact" rule into the release.md bullet that already owns the branch policy — it was missing from the OKF, and I had written a second, worse copy of the whole policy into the CI-sweep skill. That skill now states only what follows from it there. * Drop the repeated "which is how a duplicate gets filed" rationale: once, in the module header that exists to say why to use it. * Drop the second jiraClosed comment in ci-check.mjs; SKILL.md §3 is where the field is explained and the declaration already points there. * Put `earlier` on every entry, so a caller need not know whether the field or the summary fallback answered. * Look the group's issue up once instead of twice. * "four branches have run it" was this week's number, not a rule. 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