Skip to content
cccskills
FreePublished on GitHub

review

Run a lead code review on the current branch or a given PR. Standalone entry point for the lead-reviewer 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.

Review

Standalone code review for any PR. Runs the full lead-reviewer analysis against the spec and project standards. Posting inline comments and the summary to GitHub is your choice — you are prompted at the end.

Step 1 — Config

This skill targets wp-media/wp-rocket. Specs live at .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md.

Step 2 — Resolve the PR

If $ARGUMENTS is provided, use it as the PR number or URL.

Otherwise resolve from the current branch:

gh pr list --head "$(git branch --show-current)" --json number,url -q '.[0] | "\(.number) \(.url)"'

If no PR is found, tell the user and stop.

Get the base branch from the PR:

gh pr view <PR_NUMBER> --json baseRefName,body -q '{base: .baseRefName, body: .body}'

Extract the linked issue number from the PR body (Fixes #N, Closes #N, or a GitHub issue URL).

Step 3 — Locate the spec

If a linked issue number was found, check for a spec at: .TemporaryItems/Issues/wp-rocket/issues/<N>-spec.md

If it exists, pass its path to the agent. If it does not exist, inform the user: "No grooming spec found — the review will check against project standards only (spec compliance section will be skipped)."

Step 4 — Invoke the lead-reviewer agent

Invoke the lead-reviewer sub-agent with:

  • Issue number (if known) and spec path (if found, else omit)
  • Base branch from Step 2
  • PR number
  • CURRENT_MODEL: "standalone"
  • session_learnings: read Section 13 of AGENTS.md if it exists, else pass empty string
  • Repo: wp-media/wp-rocket

STANDALONE MODE — two differences from the normal pipeline run:

  1. Skip Step 5 (inline PR comments) and Step 5b (summary PR comment). Instead, output the full review report — findings table, blockers, nice-to-haves — as formatted Markdown in your response, in a section titled ## Review Report.
  2. Skip the StructuredOutput JSON return. Return a short human-readable verdict summary instead: overall verdict, blocker count, and any open questions.

Step 5 — Offer to post

After the agent responds, display its ## Review Report and ask:

Post this review to PR #<PR_NUMBER>? Reply yes to post inline comments + summary, no to finish here.

If yes — the agent posts inline comments (Step 5) and the summary comment (Step 5b) using the normal dedup flow. The <!-- ai-pipeline:lead-review --> marker ensures a later pipeline re-run updates in place rather than duplicating.

If no — confirm the review is complete and finish.

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

groom

Free

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-rocket767Updated Oct 17, 2026

See all skills by wp-media

Report a problem with this skill