القائمة
Check a change against WordPress.org plugin rules and PHPCS standards.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | compliance |
| description | Check a change against WordPress.org plugin rules and PHPCS standards. |
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.
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.
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.