Branch: refs/heads/sonarcloud-routine-prompt Home: https://github.com/xwiki/xwiki-dev-llm Commit: 5ab961b2851fcfde6b3cb8a1134a11ed3b4898a6 https://github.com/xwiki/xwiki-dev-llm/commit/5ab961b2851fcfde6b3cb8a1134a11... Author: Vincent Massol <[email protected]> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M README.md M xwiki/instructions/xwiki-org.md A xwiki/okf/architecture/platform-modules.md M xwiki/okf/index.md M xwiki/skills/xwiki-build/SKILL.md A xwiki/skills/xwiki-fix-sonarqube-issue/routine-prompt.md Log Message: ----------- [Misc] Record the SonarCloud routine's prompt and environment * Add skills/xwiki-fix-sonarqube-issue/routine-prompt.md: the prompt the scheduled routine is given, plus its variables, checkouts, setup script and memory repo. The routine lives in a config box in the web UI that nobody else can read, review or restore, so a change to it was invisible and a lost routine unrebuildable; recorded here, a change to it is a pull request * Add okf/architecture/platform-modules.md and a pnpm/Nx section to the xwiki-build skill. The prompt carried xwiki-platform's module structure, architecture and frontend facts, which are true for every session in that repo and which nothing made anyone review when they went stale. Two of its claims were in the OKF already and are dropped: never grow oldcore, and the event-listener model, both in component-system.md * Record how the routine's pull requests are opened, that being the thing most easily got wrong by reasoning from a token's permissions: the Claude GitHub App installed on the org pushes the branch into the upstream repo itself, no fork and no personal access token are involved, and the bot identity is carried by the commit author 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