メニュー
Check a change against WordPress.org plugin rules and PHPCS standards.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a bespoke issue-workflow for any target project. Phase 1 — a Claude Opus analyst reads the project deeply and produces a disposition report. Phase 2 — on approval, parallel writer agents transplant every Maestro workflow component, adapted to the target project's actual stack, test runner, dev environment, and conventions. Use when a project needs its own self-contained issue-workflow without taking a direct dependency on Maestro.
Show the Maestro command map — a quick reference to all available skills.
Adversarially review a grooming spec before implementation starts. Finds hidden risks, unvalidated assumptions, and missing dependencies. Standalone entry point for the challenger agent.
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.
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.
| name | compliance |
| description | Check a change against WordPress.org plugin rules and PHPCS standards. |
Ensure compatibility with:
Read .claude/maestro.json to load project-specific values:
TEXT_DOMAIN = .ai.text_domain (e.g. rocket, backwpup, imagify)CAPABILITIES = .ai.capabilities (project-registered custom capabilities array)HTML text: esc_html()
HTML attribute: esc_attr()
URL: esc_url()
Allowed HTML: wp_kses_post()
Use {TEXT_DOMAIN} from config for all translation calls:
esc_html__( 'Clear Cache', '{TEXT_DOMAIN}' )
esc_attr__( 'Plugin Settings', '{TEXT_DOMAIN}' )
If .ai.capabilities in .claude/maestro.json is non-empty, always use those capabilities
(not manage_options) for capability checks. The PHPCS config should allow them
without warnings.
Example — read the list from config and use accordingly:
// Correct — use the project-registered capability, not manage_options directly
current_user_can( 'plugin_manage_options' )
Using manage_options directly for plugin-specific actions is incorrect and will flag
in code review unless the project's PHPCS config explicitly allows it.
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.