Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
免费在 GitHub 公开
compliance
Check a change against WordPress.org plugin rules and PHPCS standards.
中文简介正在准备中。当前显示原文说明。
集成工具WordPress
查看安装方法包含的文件（1）
- SKILL.md2.2 KB
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
WordPress Compliance
Ensure compatibility with:
- WordPress Plugin Check
- Repository PHPCS rules
- WordPress.org expectations
Config
This skill targets wp-media/wp-rocket:
TEXT_DOMAIN=rocketCAPABILITIES= WP Rocket's registered custom capabilities (e.g.rocket_manage_options)
Responsibilities
- Respect repository PHPCS configuration.
- Follow WordPress escaping standards.
- Avoid forbidden or deprecated APIs.
- Avoid direct access to superglobals without sanitization.
- Ensure output is escaped for context.
Escaping heuristics
HTML text: esc_html()
HTML attribute: esc_attr()
URL: esc_url()
Allowed HTML: wp_kses_post()
Text domain
Use the rocket text domain for all translation calls:
esc_html__( 'Clear Cache', 'rocket' )
esc_attr__( 'WP Rocket Settings', 'rocket' )
Custom capabilities
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.
JavaScript
- Do not use jQuery. Use native DOM APIs (
document.querySelector,addEventListener,fetch, etc.). - jQuery is available in WordPress but its use introduces an unnecessary dependency and conflicts with modern bundling practices.
Anti-patterns
- Echoing raw variables
- Introducing unescaped output
- Storing sensitive values in plain text
- Bypassing repository PHPCS configuration
- Using jQuery in new or modified JS code
Related Specs
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.md
Git Operations
Follow the policy defined in AGENTS.md §5.1. Outside the issue workflow, do not run git commit or git push.
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
docs
免费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.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
dod
免费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.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
e2e
免费Run a basic E2E behavioral probe — one primary scenario smoke test for the grooming step.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
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.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新
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.
中文简介正在准备中。当前显示原文说明。
wp-media/wp-rocket7672026年10月17日 更新