Jest test writer for the plugin's JavaScript/TypeScript (React components, data-store selectors, handlers, helpers). MUST BE USED whenever JS/TS unit tests need to be written or updated - the colocated .test.js files next to module resources/js sources.
Recalls the developer's local research notes - canonical knowledge about a module/topic, plus per-task context (Jira, symptoms, findings). Read-only. Dispatch whenever you need to recall a local research note.
Records an insight into the developer's local research notes - durable canonical facts about a module/topic, or per-task context (Jira, symptoms, findings). Owns the notes' conventions and pruning. Dispatch whenever you need to record a local research note.
Read-only reviewer for PHP code cleanliness a linter cannot catch. Returns findings; never edits. Dispatch with exactly review CHANGES in (git-diff hunks only, after writing or editing) or review FULL (the entire file); no other context needed.
PHPUnit test writer for WordPress/WooCommerce PHP code. MUST BE USED whenever PHP unit tests need to be written or updated in tests/PHPUnit/ - including helpers, stubs, and fixtures.
Draft a standardized, reviewer-focused pull request description and - only after explicit approval - update the PR. Optional first argument is a PR number (defaults to the current branch's open PR). Optional argument is a Jira issue ID (e.g. ABC-123).
Manually run a PHP code-cleanliness review on a file, at higher quality than the automatic background hook. Optional first argument is FULL or CHANGES; the last argument is the PHP file path.
Run a PR readiness check on the current branch before opening or finalizing a pull request. Optional first argument is a Jira issue ID (e.g. ABC-123). Optional second argument is a base branch name.
Research and understand a module, folder, or problem before implementing, capturing what you learn as local notes. Use before starting a complex task or to deepen understanding of an area. Optional argument is a module path/name and/or a Jira issue ID (e.g. ABC-123).
AGENTS.md instructions for woocommerce/woocommerce-paypal-payments, covering agents.md, critical rules, backward compatibility, the compatibility surface is wider than php signatures and database migrations.
End-to-end implementation playbook for registering WordPress Abilities API capabilities in a WooCommerce extension. Builds on the portable skills in WordPress/agent-skills (wp-abilities-api, wp-abilities-audit, wp-abilities-verify) and adds the Woo-extension scaffolding, conventions, and PR workflow.
Audit a fixed cohort of inactive WooCommerce pull requests against current trunk, linked issues, review history, repository labels, and representative user flows, then produce evidence-backed actions and a private checklist report. Use for stale or backlog PR cohort reviews, not ordinary single-PR code review.