Skip to content
cccskills
FreePublished on GitHub

groom

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.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket
Works withGitHub
See how to install

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Groom

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.

Step 1 — Config

This skill targets wp-media/wp-rocket. The issue and spec files live at the wp-rocket temp convention:

  • Issue file: .TemporaryItems/Issues/wp-rocket/issues/<N>.md
  • Spec file: .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md

Step 2 — Sync the issue

Ensure 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.

Step 3 — Invoke the grooming agent

Invoke the grooming-agent sub-agent with the following invocation context:

Issue number: <N> Issue file path: .TemporaryItems/Issues/wp-rocket/issues/<N>.md Repo: wp-media/wp-rocket complexity_signal: derive from the issue content yourself

STANDALONE MODE — two differences from the normal pipeline run:

  1. Skip Step 5 (posting to GitHub). Instead, include the full comment body you would have posted in a section titled ## Grooming Comment Draft at 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.
  2. 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.

Step 4 — Offer to post

After the agent responds, display its ## Grooming Comment Draft to the user, then ask:

Post this as a comment on issue #<N>? Reply yes to post as-is, no to 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.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

challenge

Free

Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

compliance

Free

Check a change against WordPress.org plugin rules and PHPCS standards.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

docs

Free

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.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

dod

Free

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.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

e2e

Free

Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

issue-workflow

Free

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.

The English summary is being prepared. Showing the original description.

wp-media/wp-rocket767Updated Oct 17, 2026

See all skills by wp-media

Report a problem with this skill