| name | compliance |
| description | Check a change against WordPress.org plugin rules and PHPCS standards. |
WordPress Compliance
Ensure compatibility with:
- WordPress Plugin Check
- Repository PHPCS rules
- WordPress.org expectations
Config loading
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)
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 {TEXT_DOMAIN} from config for all translation calls:
esc_html__( 'Clear Cache', '{TEXT_DOMAIN}' )
esc_attr__( 'Plugin Settings', '{TEXT_DOMAIN}' )
Custom capabilities
If .ai.capabilities in .claude/maestro.json is non-empty, always use those capabilities
(not ) for capability checks. The PHPCS config should allow them
without warnings.