Guide

How to review a WooCommerce plugin with Claude Code

WooCommerce extensions have a different failure surface than generic WordPress plugins. You need to review order storage, payment flows, checkout behavior, templates, scheduled jobs, and performance under catalog or cart load. This guide shows how to use the wp-woocommerce-dev skill for a focused review.

When to use this workflow

Pre-release review for a WooCommerce extension
HPOS compatibility checks before a store upgrade
Payment gateway or checkout customization audits
Performance and scheduling checks for high-order-volume stores

Start with the WooCommerce-specific command

/wp-woo-review wp-content/plugins/my-woo-extension

Use the faster triage command when you want a narrower first pass:

/wp-woo wp-content/plugins/my-woo-extension

Natural language prompts that work well

Review this WooCommerce plugin for HPOS compatibility
Audit this payment gateway extension before release
Check this checkout customization for performance and hook safety
Review this WooCommerce extension for Action Scheduler and template override issues

What a strong WooCommerce review should cover

Compatibility and data model

HPOS compatibility declarations and real usage patterns
Correct WooCommerce CRUD usage instead of raw post/meta assumptions
Order lifecycle hooks and backwards-compatibility risks

Checkout and payments

Payment gateway validation and error handling
Hook timing around checkout, cart, and order status changes
Idempotency and duplicate processing risk

Templates and frontend behavior

Template overrides that drift from WooCommerce hooks
Cart fragments, mini-cart behavior, and unnecessary asset loading
Frontend actions that trigger expensive or repeated work

Scheduling and scale

Action Scheduler usage and retry behavior
Background jobs that may pile up under load
Query and cache patterns that get expensive on larger catalogs

Example output shape

Critical — Extension reads order data from legacy post meta paths without HPOS-safe abstraction
- File: includes/class-order-sync.php:143
- Why it matters: order reads and writes may break or behave inconsistently on HPOS-enabled stores
- Fix: move to WooCommerce CRUD accessors and verify compatibility declarations match real behavior

Warning — Action Scheduler job can be queued repeatedly without a duplicate guard
- File: includes/class-renewal-runner.php:77
- Why it matters: repeated scheduling can create duplicate side effects and queue pressure on busy stores
- Fix: add a uniqueness guard and review retry behavior for failures

Related review commands

/wp-sec-review for deeper security review
/wp-perf-review for performance-heavy extensions
/wp-test-review to turn findings into a WooCommerce test plan
/wp-migration-review when the extension includes schema or data migrations