Check a change against WordPress.org plugin rules and PHPCS standards.
The English summary is being prepared. Showing the original description.
Review the instructions the agent will receive before you install.
Ensure compatibility with:
This skill targets wp-media/wp-rocket:
TEXT_DOMAIN = rocketCAPABILITIES = WP Rocket's registered custom capabilities (e.g. rocket_manage_options)HTML text: esc_html()
HTML attribute: esc_attr()
URL: esc_url()
Allowed HTML: wp_kses_post()
Use the rocket text domain for all translation calls:
esc_html__( 'Clear Cache', 'rocket' )
esc_attr__( 'WP Rocket Settings', 'rocket' )
WP Rocket registers custom capabilities. Always use those (not manage_options) for
capability checks. PHPCS is configured to allow them without warnings:
// Correct — use the WP Rocket–registered capability, not manage_options directly
current_user_can( 'rocket_manage_options' )
Using manage_options directly for WP Rocket–specific actions is incorrect and will flag
in code review.
document.querySelector, addEventListener, fetch, etc.).When relevant, consult repository specs under .claude/specs/, especially:
.claude/specs/phpcs/nonce-verification-recommended.md.claude/specs/phpcs/validated-sanitized-input.md.claude/specs/phpcs/escaped-output.mdFollow the policy defined in AGENTS.md §5.1. Outside the issue workflow, do not run git commit or git push.
No reviews yet. Tell others what you thought.
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.
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.
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.
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.
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.
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.
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.