Woocommerce Code Review
Testing & Qualitywoocommerce-code-reviewWoocommerce Code Review is an Agent Skill for testing & quality published in the woocommerce/woocommerce repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/woocommerce/woocommerce/blob/HEAD/.ai/skills/woocommerce-code-review/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/woocommerce-code-review, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
WooCommerce Code Review
Review code changes against WooCommerce coding standards and conventions.
Critical Violations to Flag
Backend PHP Code
Consult the woocommerce-backend-dev skill for detailed standards. Using these standards as guidance, flag these violations and other similar ones:
Architecture & Structure:
- ❌ Standalone functions - Must use class methods (file-entities.md)
- ❌ Using
newfor DI-managed classes - Classes insrc/must use$container->get()(dependency-injection.md) - ❌ Classes outside
src/Internal/- Default location unless explicitly public (file-entities.md)
Naming & Conventions:
- ❌ camelCase naming - Must use snake_case for methods/variables/hooks (code-entities.md)
- ❌ Yoda condition violations - Must follow WordPress Coding Standards (coding-conventions.md)
Documentation:
- ❌ Missing
@sinceannotations - Required for public/protected methods and hooks (code-entities.md) - ❌ Missing docblocks - Required for all hooks and methods (code-entities.md)
- ❌ Verbose docblocks - Keep concise, one line is ideal (code-entities.md)
Data Integrity:
- ❌ Missing validation - Must verify state before deletion/modification (data-integrity.md)
Testing:
- ❌ Using
$instancein tests - Must use$sutvariable name (unit-tests.md) - ❌ Missing
@testdox- Required in test method docblocks (unit-tests.md) - ❌ Test file naming - Must follow convention for
includes/vssrc/(unit-tests.md)
Frontend JS/TS Code
Architecture & Structure:
- ❌ Barrel self-import (circular dependency) — a JS/TS file anywhere in the monorepo importing from its own package barrel (
from '../',from '../../',from '../index',from '../../index') when that barrel re-exports it. Relevant to SWC TDZ / esbuild tree-shaking / tsc incremental builds. Fix: use the direct module path instead.
UI Text & Copy
Consult the woocommerce-copy-guidelines skill. Flag:
- ❌ Title Case in UI - Must use sentence case (sentence-case.md)
- Wrong: "Save Changes", "Order Details", "Payment Options"
- Correct: "Save changes", "Order details", "Payment options"
- Exceptions: Proper nouns (WooPayments), acronyms (API), brand names
Review Approach
- Scan for critical violations listed above
- Cite specific skill files when flagging issues
- Provide correct examples from the skill documentation
- Group related issues for clarity
- Be constructive - explain why the standard exists when relevant
Output Format
For each violation found:
❌ [Issue Type]: [Specific problem]
Location: [File path and line number]
Standard: [Link to relevant skill file]
Fix: [Brief explanation or example]
Notes
- All detailed standards are in the
woocommerce-backend-dev,woocommerce-dev-cycle, andwoocommerce-copy-guidelinesskills - Consult those skills for complete context and examples
- When in doubt, refer to the specific skill documentation linked above