Branch: refs/heads/sonarcloud-routine-prompt Home: https://github.com/xwiki/xwiki-dev-llm Commit: c10ded1b1771de462f8665c98937572bd734a100 https://github.com/xwiki/xwiki-dev-llm/commit/c10ded1b1771de462f8665c9893757... 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 record of the scheduled SonarCloud routine: the prompt verbatim, the variables it is given, the repos it has checked out, the setup script it runs, and the memory repo it reads and writes. 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. Mirrors what xwiki-ci-check already carries * Record how the routine's pull requests are actually 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. GH_TOKEN is the bot's, which the memory repo's own history shows * Note the memory repo's pending move from vmassol/claude-routine-memory to xwikiorg-llm-bot/sonarcloud-routine-memory, so that the routine's memory belongs to the routine's identity rather than to a person, and name the three things that change together when it moves * Move the XWiki knowledge out of the prompt and into the plugin, where every session gets it and where it is reviewed when it goes stale: add okf/architecture/platform-modules.md (the tools/core/distribution split, the modules worth knowing by name, the OSGi manifest each JAR carries and what xwiki.extension.features advertises) and a pnpm/Nx section to the xwiki-build skill, that being a build procedure rather than declarative knowledge. Two of the prompt's claims were in the OKF already and are simply dropped: never grow oldcore, and the event-listener model, both in component-system.md and the latter in more detail than the prompt had it * Rewrite the prompt around what is left: the three repositories named once at the top rather than one of them in the first sentence and two in a later bullet, the memory protocol as one block rather than a sentence and two overlapping bullets, dropped-issues.md named rather than "somewhere in the memory files", and "assign it to me" as "assign it to vmassol" — a routine has no "me" to resolve the pronoun against * Drop SONARQUBE_PROJECT_KEY from the routine's environment: it names one SonarCloud project and the routine sweeps three, so any value was wrong for two of them. Nothing depended on it, the MCP server declaring it optional and resolving the project per workspace; it stays in .mcp.json for the developer case of one checkout, one project 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