Branch: refs/heads/okf-commit-message-title-rule Home: https://github.com/xwiki/xwiki-dev-llm Commit: 3d2f658627c247b9ee0bb00fb063555291fd4b9a https://github.com/xwiki/xwiki-dev-llm/commit/3d2f658627c247b9ee0bb00fb06355... Author: Vincent Massol <[email protected]> Date: 2026-08-06 (Thu, 06 Aug 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json M xwiki/instructions/xwiki-org.md M xwiki/okf/conventions/commit-messages.md M xwiki/okf/index.md M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] Correct the commit-message convention: the summary line is the JIRA issue title * The OKF, the always-injected org instructions and the xwiki-pull-request skill all documented the format as `XWIKI-12345: <summary>`, which reads as an invitation to compose a new sentence. The documented rule is `<JIRA ID>: <JIRA issue description>` — the issue title reproduced verbatim — with what the individual commit does listed as `*` bullets in the body. * Record why the body matters: it is the only thing distinguishing several commits that share one issue, since their summary lines are identical by construction. * Record the corollary that the title is reused on every commit and so must read well as a commit summary, and must not be reworded casually afterwards. * Scope `[Misc]` using the dev-wiki test ("does it affect any user or extension developer?") so a behaviour-changing batch refactoring is not filed under it. * Note that security fixes override the copy-the-title rule, since the title would disclose the nature of the issue before it is released. * Add the JIRA best-practices page, which actually carries the rule, to the entry's sources. * Bump the plugin version to 1.0.13 so installed plugins pull the update. 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