Branch: refs/heads/ci-check-repeat-oracle Home: https://github.com/xwiki/xwiki-dev-llm Commit: 06aa6a40027560d5090a48512dd16cca99777f72 https://github.com/xwiki/xwiki-dev-llm/commit/06aa6a40027560d5090a48512dd16c... Author: Vincent Massol <[email protected]> Date: 2026-09-19 (Sat, 19 Sep 2026) Changed paths: M xwiki/skills/xwiki-fix-flickering-docker-test/SKILL.md Log Message: ----------- [Misc] Keep the flickering-test skill about fixing a flickering test * Drop the release-priority paragraph and the "in a routine, launch without asking" clause: which red thing a scheduled sweep should spend its budget on is xwiki-ci-check's question, not one a developer fixing a named flicker ever asks * Cut the implementation rationale (why the external engine implies jetty_standalone) down to the constraint a caller acts on, and drop the framing that sold the tool rather than explaining it * Keep, tightened: why a rate rather than a pass, how to read a setup error, how many repetitions are worth running, reuse versus fresh, and the cost of taking a developer's machine 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