Branch: refs/heads/add-xwiki-review-skill Home: https://github.com/xwiki/xwiki-dev-llm Commit: 16b1bf9db8711fbb4726db8dde28d34b0dc6813e https://github.com/xwiki/xwiki-dev-llm/commit/16b1bf9db8711fbb4726db8dde28d3... Author: Vincent Massol <[email protected]> Date: 2026-08-12 (Wed, 12 Aug 2026) Changed paths: M .claude-plugin/marketplace.json M README.md M kimi.plugin.json M opencode.jsonc M scripts/validate.mjs M xwiki/.claude-plugin/plugin.json M xwiki/okf/index.md A xwiki/skills/xwiki-review/SKILL.md Log Message: ----------- [Misc] Add the xwiki-review skill for multi-angle change review * Add `xwiki/skills/xwiki-review/SKILL.md`, a review procedure that fans out one specialist reviewer per angle — conventions, architecture, backward compatibility, defensive conventions, performance, tests, accessibility, i18n/UX, documentation, data & migration, and conformance to the JIRA issue — over a PR, a commit range or the working tree, routing each angle in or out from the changed-file profile. * Keep the rules in the OKF rather than in the skill: each brief names the OKF files and skills to load and what to look at, never what the rule says, so a rule has exactly one home. A paraphrase would drift, and would fail silently — the skeptic in step 5 scores a finding 0 when the cited file does not say what was claimed, so a stale copy makes an angle report nothing rather than report wrongly. Checks with no OKF home are marked skill-owned, as a to-do list for the EXTEND flow. * Gate the output: deduplicate across angles, challenge each finding with an independent skeptic that must open the cited rule and confirm it, drop everything below 80 confidence, cap the report, and open every posted review with a disclaimer that it was generated by Claude Code, may be wrong, and blocks nothing. * Keep the defensive-conventions angle to the mechanisms `okf/conventions/security.md` requires and ban security vocabulary in findings, reasoning and logs alike — public CI logs are public, so the angle reports a missing mechanism and never an attack, per `okf/processes/security-policy.md`. Hunting novel vulnerabilities is explicitly out of scope. * Add invariant 5 to `scripts/validate.mjs`: every `okf/<dir>/<topic>.md` path a skill cites must exist, so a renamed or deleted topic fails CI instead of leaving a reviewer pointing at nothing. * Register the skill in `README.md` and `xwiki/okf/index.md`, and bump the plugin version to 1.0.18 across the Claude, Kimi and opencode manifests. 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