September 2026 - notifications

[xwiki/xwiki-dev-llm] 4f0624: [Misc] Block unescaped GitHub autolinks in commit ...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/commit-message-at-escaping Home: https://github.com/xwiki/xwiki-dev-llm Commit: 4f0624ca5bbfb958b12990c277bbee28d62b8f9c https://github.com/xwiki/xwiki-dev-llm/commit/4f0624ca5bbfb958b12990c277bbe… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M README.md M kimi.plugin.json M xwiki/hooks/hooks.json M xwiki/okf/conventions/commit-messages.md A xwiki/opencode/plugins/xwiki-commit-text.js A xwiki/scripts/check-commit-text.mjs M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] Block unescaped GitHub autolinks in commit and PR text with a hook * GitHub autolinks a bare `@name` in a commit body or PR body: `@since` links to and notifies the GitHub account of that name, an unrelated third party (`param`, `deprecated`, `Inject`, `Component`, `Override`, `UITest` and `Nested` are all real accounts too). A `#123` written by hand resolves against the GitHub repo, while XWiki's issues live in JIRA. Backticks suppress the autolink even though a commit message renders no other markup. * Enforce it with `check-commit-text.mjs`, a `PreToolUse` hook on `Bash` that inspects the message a `git commit` or `gh pr create`/`gh pr edit` would write and refuses it on a violation. The damage is unfixable after the fact — a pushed commit message can only be corrected by rewriting history on a shared branch — so this is blocked rather than documented and hoped for. Same rationale and shape as the line-ending guard: silent unless violated, Node, no always-on cost. * Parse a shell wrapper too: Claude Code resolves `bash -c "git commit …"` to the command `bash` and does not look inside the `-c` string, so a wrapped commit would otherwise bypass the check entirely. The inner script is re-parsed as a command in its own right, bounded to three levels. Scanning the raw command string instead was rejected: it blocks commands over text that was never a message, its advice (add backticks) is wrong for a shell command, and it cannot keep the summary-line exemption — 39 of 900 sampled commit subjects in these repos carry a bare `@` token. * Gate each handler with `if` (`Bash(git commit*)`, `Bash(gh pr*)`, and the three shell wrappers) so Claude Code matches the command string before spawning anything. Node's ~35 ms startup is the entire cost of this check — the check itself is 3 µs on a real commit and 224 µs on a 100 KB worst case — and without the gate every shell command would pay it. * Exempt the commit summary line: the convention is that it is the JIRA issue title verbatim, so it cannot take backticks. A bare token there is fixed by renaming the issue. Leave the `(#6304)` GitHub's squash merge appends alone. * Register the hook for all three hosts, with an opencode plugin wrapper reusing the same logic. * Document the rule in the commit-messages OKF topic and the `xwiki-pull-request` skill, and the capability in README.md. * Leave `xwiki/instructions/xwiki-org.md` and its byte budget untouched: the hook is what prevents a recurrence, so the always-on file does not need to carry the rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 9e789b: [Misc] Block unescaped GitHub autolinks in commit ...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/commit-message-at-escaping Home: https://github.com/xwiki/xwiki-dev-llm Commit: 9e789ba81cff2c04ddbe249a85cde45528c5050b https://github.com/xwiki/xwiki-dev-llm/commit/9e789ba81cff2c04ddbe249a85cde… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M README.md M kimi.plugin.json M xwiki/hooks/hooks.json M xwiki/okf/conventions/commit-messages.md A xwiki/opencode/plugins/xwiki-commit-text.js A xwiki/scripts/check-commit-text.mjs M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] Block unescaped GitHub autolinks in commit and PR text with a hook * GitHub autolinks a bare `@name` in a commit body or PR body: `@since` links to and notifies the GitHub account of that name, an unrelated third party (`param`, `deprecated`, `Inject`, `Component`, `Override`, `UITest` and `Nested` are all real accounts too). A `#123` written by hand resolves against the GitHub repo, while XWiki's issues live in JIRA. Backticks suppress the autolink even though a commit message renders no other markup. * Enforce it with `check-commit-text.mjs`, a `PreToolUse` hook on `Bash` that inspects the message a `git commit` or `gh pr create`/`gh pr edit` would write and refuses it on a violation. The damage is unfixable after the fact — a pushed commit message can only be corrected by rewriting history on a shared branch — so this is blocked rather than documented and hoped for. Same rationale and shape as the line-ending guard: silent unless violated, Node, no always-on cost. * Parse a shell wrapper too: Claude Code resolves `bash -c "git commit …"` to the command `bash` and does not look inside the `-c` string, so a wrapped commit would otherwise bypass the check entirely. The inner script is re-parsed as a command in its own right, bounded to three levels. Scanning the raw command string instead was rejected: it blocks commands over text that was never a message, its advice (add backticks) is wrong for a shell command, and it cannot keep the summary-line exemption — 39 of 900 sampled commit subjects in these repos carry a bare `@` token. * Gate each handler with `if` (`Bash(git commit*)`, `Bash(gh pr*)`, and the three shell wrappers) so Claude Code matches the command string before spawning anything. Node's ~35 ms startup is the entire cost of this check — the check itself is 3 µs on a real commit and 224 µs on a 100 KB worst case — and without the gate every shell command would pay it. * Exempt the commit summary line: the convention is that it is the JIRA issue title verbatim, so it cannot take backticks. A bare token there is fixed by renaming the issue. Leave the `(#6304)` GitHub's squash merge appends alone. * Register the hook for all three hosts, with an opencode plugin wrapper reusing the same logic. * Document the rule in the commit-messages OKF topic and the `xwiki-pull-request` skill, and the capability in README.md. * Leave `xwiki/instructions/xwiki-org.md` and its byte budget untouched: the hook is what prevents a recurrence, so the always-on file does not need to carry the rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 67bf0f: [Misc] Fix three unparseable skill frontmatters an...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/skill-frontmatter-yaml Home: https://github.com/xwiki/xwiki-dev-llm Commit: 67bf0ff4e971645df5d628b0327537f7b37d49e0 https://github.com/xwiki/xwiki-dev-llm/commit/67bf0ff4e971645df5d628b032753… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M scripts/validate.mjs M xwiki/skills/xwiki-openproject/SKILL.md M xwiki/skills/xwiki-release-test-triage/SKILL.md M xwiki/skills/xwiki-test-guidelines/SKILL.md Log Message: ----------- [Misc] Fix three unparseable skill frontmatters and validate them * `xwiki-test-guidelines`, `xwiki-openproject` and `xwiki-release-test-triage` each carry a colon-space inside an unquoted (plain) YAML scalar, which makes the whole frontmatter block unparseable. The host then loads the skill with EMPTY metadata instead of failing, so the `description` Claude matches on is gone and the skill never triggers — a silent, total loss of three skills. Measured with the `yaml` package: all three throw "Nested mappings are not allowed in compact mappings". Replace the colon with an em dash, which reads the same. * Add invariant 9 to `scripts/validate.mjs`: no `: ` or ` #` inside an unquoted frontmatter scalar, continuation lines included, and no leading YAML indicator character. A quoted or block scalar is left alone — several descriptions rely on that. * This does not duplicate `claude plugin validate`, which is weaker: with all three offenders present it named one, then passed the repo. CI runs `validate.mjs`, so the invariant is what actually gates a branch. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 1942e7: [Misc] Block unescaped GitHub autolinks in commit ...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/commit-message-at-escaping Home: https://github.com/xwiki/xwiki-dev-llm Commit: 1942e73397b9b9217c9a018bee2bf222d21eb3d5 https://github.com/xwiki/xwiki-dev-llm/commit/1942e73397b9b9217c9a018bee2bf… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M README.md M kimi.plugin.json M xwiki/hooks/hooks.json M xwiki/okf/conventions/commit-messages.md A xwiki/opencode/plugins/xwiki-commit-text.js A xwiki/scripts/check-commit-text.mjs M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] Block unescaped GitHub autolinks in commit and PR text with a hook * GitHub autolinks a bare `@name` in a commit body or PR body: `@since` links to and notifies the GitHub account of that name, an unrelated third party (`param`, `deprecated`, `Inject`, `Component`, `Override`, `UITest` and `Nested` are all real accounts too). A `#123` written by hand resolves against the GitHub repo, while XWiki's issues live in JIRA. Backticks suppress the autolink even though a commit message renders no other markup. * Enforce it with `check-commit-text.mjs`, a `PreToolUse` hook on `Bash` that inspects the message a `git commit` or `gh pr create`/`gh pr edit` would write and refuses it on a violation. The damage is unfixable after the fact — a pushed commit message can only be corrected by rewriting history on a shared branch — so this is blocked rather than documented and hoped for. Same rationale and shape as the line-ending guard: silent unless violated, Node, no always-on cost. * Gate each handler with `if` (`Bash(git commit*)`, `Bash(gh pr*)`) so Claude Code matches the command string before spawning anything. Node's ~35 ms startup is the entire cost of this check, and without the gate every shell command would pay it. The filter errs toward running the hook, which is the safe direction. * Exempt the commit summary line: the convention is that it is the JIRA issue title verbatim, so it cannot take backticks. A bare token there is fixed by renaming the issue. Leave the `(#6304)` GitHub's squash merge appends alone. * Register the hook for all three hosts, with an opencode plugin wrapper reusing the same logic. * Document the rule in the commit-messages OKF topic and the `xwiki-pull-request` skill, and the capability in README.md. * Leave `xwiki/instructions/xwiki-org.md` and its byte budget untouched: the hook is what prevents a recurrence, so the always-on file does not need to carry the rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm] 9b4f2f: [Misc] Block unescaped GitHub autolinks in commit ...
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/commit-message-at-escaping Home: https://github.com/xwiki/xwiki-dev-llm Commit: 9b4f2f68c445dd077fc59164475134e80b6a33c2 https://github.com/xwiki/xwiki-dev-llm/commit/9b4f2f68c445dd077fc5916447513… Author: Vincent Massol <vincent(a)massol.net> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M README.md M kimi.plugin.json M xwiki/hooks/hooks.json M xwiki/okf/conventions/commit-messages.md A xwiki/opencode/plugins/xwiki-commit-text.js A xwiki/scripts/check-commit-text.mjs M xwiki/skills/xwiki-pull-request/SKILL.md Log Message: ----------- [Misc] Block unescaped GitHub autolinks in commit and PR text with a hook * GitHub autolinks a bare `@name` in a commit body or PR body: `@since` links to and notifies the GitHub account of that name, an unrelated third party (`param`, `deprecated`, `Inject`, `Component`, `Override`, `UITest` and `Nested` are all real accounts too). A `#123` written by hand resolves against the GitHub repo, while XWiki's issues live in JIRA. Backticks suppress the autolink even though a commit message renders no other markup. * Enforce it with `check-commit-text.mjs`, a `PreToolUse` hook on `Bash` that inspects the message a `git commit` or `gh pr create`/`gh pr edit` would write and refuses it on a violation. The damage is unfixable after the fact — a pushed commit message can only be corrected by rewriting history on a shared branch — so this is blocked rather than documented and hoped for. Same rationale and shape as the line-ending guard: silent unless violated, Node, no always-on cost. * Exempt the commit summary line: the convention is that it is the JIRA issue title verbatim, so it cannot take backticks. A bare token there is fixed by renaming the issue. Leave the `(#6304)` GitHub's squash merge appends alone. * Register the hook for all three hosts, with an opencode plugin wrapper reusing the same logic. * Document the rule in the commit-messages OKF topic and the `xwiki-pull-request` skill, and the capability in README.md. * Leave `xwiki/instructions/xwiki-org.md` and its byte budget untouched: the hook is what prevents a recurrence, so the always-on file does not need to carry the rule. Co-Authored-By: Claude Opus 5 (1M context) <noreply(a)anthropic.com> To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[[email protected]][Issue] Updates for XWIKI-25012: Child pages of a page with a dot in its name disappear from the page tree when the parent page is deleted
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0

[[email protected]][Issue] Updates for XWIKI-6161: Reset action does not work anymore
by XWiki Notifications 17 Sep '26

17 Sep '26

1 0

[xwiki/xwiki-dev-llm] 6c24d9: [Misc] Release 1.11.4
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/master Home: https://github.com/xwiki/xwiki-dev-llm Commit: 6c24d9bb6c37049517ca4278ed06ac54253a50fd https://github.com/xwiki/xwiki-dev-llm/commit/6c24d9bb6c37049517ca4278ed06a… Author: github-actions[bot] <41898282+github-actions[bot](a)users.noreply.github.com> Date: 2026-09-17 (Thu, 17 Sep 2026) Changed paths: M .claude-plugin/marketplace.json M kimi.plugin.json M opencode.jsonc M xwiki/.claude-plugin/plugin.json Log Message: ----------- [Misc] Release 1.11.4 * content edits only (no capability added or removed) To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/tags/v1.11.4 Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0

[xwiki/xwiki-dev-llm]
by XWiki Notifications 17 Sep '26

17 Sep '26

Branch: refs/heads/advisory-app-import Home: https://github.com/xwiki/xwiki-dev-llm To unsubscribe from these emails, change your notification settings at https://github.com/xwiki/xwiki-dev-llm/settings/notifications

1 0