Claude Skills by wp-media

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.

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.

Read and refresh wp-rocket's pre-built dependency graph at .claude/graph/dependency-graph.json. Use to locate a class file, trace dependencies, find the ServiceProvider that wires a service, or enumerate Subscribers in a module — without re-scanning the codebase from scratch. This skill is primarily a reader: the graph is built (and incrementally refreshed) by `node bin/build-knowledge-graph.js`. Invoke this skill at session start (to refresh if stale) and before grep/glob searches for class ...

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, m...

Run QA validation on a pull request — boots the local environment, tests acceptance criteria, and optionally posts the report as a PR comment. Standalone entry point for the qa-engineer agent.

Run a lead code review on the current branch or a given PR. Standalone entry point for the lead-reviewer agent.

Use this skill when adding or modifying WordPress abilities

Use this skill when modifying templates, admin UI, output, hooks, plugin metadata, sanitization, escaping, or any code that must remain compliant with WordPress.org and repository PHPCS rules.

Use this skill when changing service structure, Subscribers, ServiceProviders, Container wiring, bootstrapping, Context classes, or any code that may affect the core caching engine in WP Rocket.

Use this skill when changing admin JavaScript, CSS, or HTML/Twig templates in WP Rocket.