Branch: refs/heads/vmassol/ci-check-tool-rules Home: https://github.com/xwiki/xwiki-dev-llm Commit: b38fa3e6047d077c5e9571363f2c480a90e63143 https://github.com/xwiki/xwiki-dev-llm/commit/b38fa3e6047d077c5e9571363f2c48... Author: Vincent Massol <[email protected]> Date: 2026-10-14 (Wed, 14 Oct 2026) Changed paths: M xwiki/scripts/jenkins.mjs M xwiki/scripts/jira-flickers.mjs M xwiki/skills/xwiki-ci-check/SKILL.md M xwiki/skills/xwiki-ci-check/references/deep-analysis.md M xwiki/skills/xwiki-ci-check/references/fix-signals.md M xwiki/skills/xwiki-ci-check/references/flicker-issues.md M xwiki/skills/xwiki-ci-check/references/local-run.md M xwiki/skills/xwiki-ci-check/references/paste.md M xwiki/skills/xwiki-ci-check/references/quality-gate.md M xwiki/skills/xwiki-ci-check/tools/ci-check.mjs Log Message: ----------- [Misc] CI check skill: fix the gaps the trial and the routine dry run found (#274) * jira-flickers.mjs: closed flicker issues carry `resolution`; ci-check.mjs no longer prints "closed as fixed" or "already fixed" for one closed Cannot Reproduce / Won't Fix (XWIKI-22818, XWIKI-18540), and fix-signals.md says such an issue is no backport candidate. * ci-check.mjs: `flickerGroup` only on the incident that carries the cause, never on a `primary: false` peer, which also stops the paste dropping a group member (HomepageTourIT on 18.4.x); flicker-issues.md loses the paragraph the code now applies. * ci-check.mjs: `summary.stabilise.blockers` lists every blocker, not the first five; `summary.stabilise.configuration` is the worst configuration on the pick's own branch. * ci-check.mjs: the stale-snapshot check counts `-pageobjects/src/main/` as taken from Nexus, so a commit adding a page-object method and the IT calling it is recognised (LikeIT, PanelsAdministrationIT). * jenkins.mjs: drops script and style content when turning a log page into lines, so the Cloudflare beacon no longer lands in `evidence`. * SKILL.md, deep-analysis.md, flicker-issues.md, paste.md: "an incident with a fixState" becomes one a fixState answers whole, matching the code (a `partial` or `candidate` answer leaves the incident live). * SKILL.md: the description no longer says a local run never touches JIRA (§0 and flicker-issues.md ask before filing), the §0 row covers a comment on a closed issue, and §1 says the run's files go to a scratch directory. * fix-signals.md: no JIRA comment naming the line release.md keeps out of public artifacts; quality-gate.md: a routine opens the gate fix PR with pull-request.mjs, not the gh that xwiki-fix-sonarqube-issue names; local-run.md: a local fix PR is asked about before it is prepared. Co-authored-by: Claude Opus 5.5 (1M context) <[email protected]> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications