メニュー
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.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
User-facing entry point for the wp-rocket issue workflow. Invoke directly to start a delivery run from a GitHub issue number, URL, or raw description. Runs inline in your conversation context; spawns specialist agents (ticket-writer, grooming-agent, challenger, backend-agent, frontend-agent, release-agent, lead-reviewer, qa-engineer) as isolated sub-agents; invokes supporting skills (knowledge-graph, dod, docs, issue-workflow) inline. Routes based on structured JSON outputs from each agent, manages loop counters, handles escalations, and maintains a live HTML run log.
Use this skill when adding or modifying WordPress abilities
Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
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.
| name | groom |
| description | 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. |
| argument-hint | <issue-number> |
Standalone grooming for a single issue. Runs the full grooming analysis and writes the spec to disk. Posting to GitHub is your choice — you are prompted at the end.
This skill targets wp-media/wp-rocket. The issue and spec files live at the wp-rocket
temp convention:
.TemporaryItems/Issues/wp-rocket/issues/<N>.md.TemporaryItems/Issues/wp-rocket/issues/<N>-spec.mdEnsure the issue file exists at .TemporaryItems/Issues/wp-rocket/issues/<N>.md. Run:
bash .claude/skills/issue-workflow/scripts/issue-sync.sh <N>
If the file already exists and is recent (less than 5 minutes old), skip the sync.
Invoke the grooming-agent sub-agent with the following invocation context:
Issue number:
<N>Issue file path:.TemporaryItems/Issues/wp-rocket/issues/<N>.mdRepo:wp-media/wp-rocketcomplexity_signal: derive from the issue content yourselfSTANDALONE MODE — two differences from the normal pipeline run:
- Skip Step 5 (posting to GitHub). Instead, include the full comment body you would have posted in a section titled
## Grooming Comment Draftat the end of your response. Use exactly the same format the pipeline would post (including the<!-- ai-pipeline:grooming-plan -->marker), so it is ready to post as-is.- Skip the StructuredOutput JSON return. Return a short human-readable summary instead: effort, risk, complexity, and any open questions.
The spec file is still written to .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md as normal.
After the agent responds, display its ## Grooming Comment Draft to the user, then ask:
Post this as a comment on issue #<N>? Reply
yesto post as-is,noto finish without posting, or paste edited text to post a modified version.
If yes — check for an existing grooming comment first (dedup):
EXISTING_ID=$(gh api repos/wp-media/wp-rocket/issues/<N>/comments \
--jq '[.[] | select(.body | contains("<!-- ai-pipeline:grooming-plan -->"))] | 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.
If no — confirm the spec was written to .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md and finish.
If edited — use the user-provided text as the comment body and post.