Check a change against WordPress.org plugin rules and PHPCS standards.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Standalone adversarial spec review. Runs the full challenger analysis on an existing grooming spec and outputs a verdict (APPROVED / NEEDS_REVISION / BLOCKED) with MoSCoW-classified findings. Posting to the GitHub issue is your choice — you are prompted at the end.
This skill targets wp-media/wp-rocket. Use $ARGUMENTS as the issue number N. Verify both files exist:
.TemporaryItems/Issues/wp-rocket/issues/<N>.md.TemporaryItems/Issues/wp-rocket/issues/<N>-spec.mdIf the spec does not exist, tell the user: "No spec found for issue #N. Run /groom <N>
first to produce one." Stop here.
If only the issue file is missing, sync it:
bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>
Invoke the challenger sub-agent with:
N.TemporaryItems/Issues/wp-rocket/issues/<N>.md.TemporaryItems/Issues/wp-rocket/issues/<N>-spec.mdplan_version: 1 (or detect from the spec's Plan v<N> header if present)CURRENT_MODEL: "standalone"session_learnings: read Section 13 of AGENTS.md if it exists, else pass empty stringwp-media/wp-rocketSTANDALONE MODE — one difference from the normal pipeline run: Skip the StructuredOutput JSON return. Output the full human-readable verdict (APPROVED / NEEDS_REVISION / BLOCKED) and findings in a section titled
## Challenge Report, using the same format the orchestrator would receive (verdict, MoSCoW-classified findings, alternative suggestions).
After the agent responds, display its ## Challenge Report and ask:
Post this challenge report as a comment on issue #<N>? Reply
yesto post,noto finish here.
If yes — post with dedup:
EXISTING_ID=$(gh api repos/wp-media/wp-rocket/issues/<N>/comments \
--jq '[.[] | select(.body | contains("<!-- ai-pipeline:challenge -->"))] | last | .id // empty')
Update with gh api --method PATCH repos/wp-media/wp-rocket/issues/comments/$EXISTING_ID if found, otherwise post a new comment. Body always starts with <!-- ai-pipeline:challenge -->.
If no — finish. Remind the user: if the verdict is NEEDS_REVISION, update the spec at
.TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md before running /groom <N> again or starting implementation.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Check a change against WordPress.org plugin rules and PHPCS standards.
日本語の概要は準備中です。原文の説明を表示しています。
Update developer-facing documentation to reflect code changes on the current branch. Runs as an inline skill inside backend-agent and frontend-agent (step 2.5 of the internal sequence) after implementation and before DOD. Receives the explicit list of changed files from the implementation agent. No-op if no public API changes occurred.
日本語の概要は準備中です。原文の説明を表示しています。
Run the Definition of Done checklist for the current wp-rocket branch and report PASS/WARN/FAIL with evidence. Two modes: layer 1 (self-correction inside backend-agent / frontend-agent — resolves FAILs before handoff) and layer 2 (independent orchestrator gate — fresh perspective after handoff). Pass layer: "1" or layer: "2" when invoking.
日本語の概要は準備中です。原文の説明を表示しています。
Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.
日本語の概要は準備中です。原文の説明を表示しています。
Groom a single GitHub issue — produce an implementation spec and optionally post the grooming summary as a GitHub comment. Standalone entry point for the grooming-agent.
日本語の概要は準備中です。原文の説明を表示しています。
Work on a GitHub issue by number for wp-media/wp-rocket. Fetches the issue and hands control to the orchestrator skill (running inline in this conversation), which manages grooming, spec review, implementation, lead review, CI, and QA end-to-end.
日本語の概要は準備中です。原文の説明を表示しています。