Menü
Check a change against WordPress.org plugin rules and PHPCS standards.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Run the Definition of Done checklist for the current branch — PASS/WARN/FAIL with evidence.
Start a full delivery run from a GitHub issue number, URL, or raw description.
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.
Run E2E smoke tests (basic) or full acceptance + regression suite (extended).
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:
The following values are injected via the orchestrator prompt — do not read any config file:
TEXT_DOMAIN = imagifyCAPABILITIES = project-registered custom capabilities (see orchestrator Project Config block)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 the project defines custom capabilities, always use those
(not manage_options) for capability checks. The PHPCS config should allow them
without warnings.
Example — use the project-registered capability, not manage_options directly:
// 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.