woo-guard

Review WooCommerce code changes for HPOS incompatibilities, CRUD bypasses, and checkout validation gaps.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/basmawebinfo-hub/lover-diet-center --skill woo-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: woo-guard
Source: https://github.com/basmawebinfo-hub/lover-diet-center/tree/main/.opencode/skills/woo-guard
Command: npx skills add https://github.com/basmawebinfo-hub/lover-diet-center --skill woo-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps prevent WooCommerce code from shipping with compatibility, checkout, pricing, and data-access mistakes that can break stores or cause financial errors. It is especially useful when AI-generated or recently edited code touches orders, products, checkout flows, gateways, stock, or WooCommerce hooks.

Core Features & Use Cases

  • HPOS-safe code review: Flags legacy order access patterns like post meta reads and shop_order queries that fail on High-Performance Order Storage stores.
  • CRUD and checkout enforcement: Verifies that orders, products, customers, and coupons use WooCommerce CRUD APIs and that checkout validation happens server-side for legacy checkout, Blocks, or both.
  • Money and runtime safeguards: Detects float-based price handling, unsafe cart or session access, missing compatibility declarations, and fragile template overrides.
  • Use Case: Review a WooCommerce plugin update after adding a checkout field, changing order metadata, or integrating a payment callback to catch HPOS breakage, skipped hooks, and pricing errors before deployment.

Quick Start

Ask the AI to use woo-guard to review your changed WooCommerce files for HPOS compatibility, CRUD correctness, checkout validation, and money-handling issues.

Frequently Asked Questions about woo-guard

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check WooCommerce code for HPOS compatibility issues?

To check WooCommerce code for HPOS compatibility, review changes for legacy post meta reads and shop_order queries that fail on High-Performance Order Storage stores. Flag direct database access and enforce storage-agnostic order access patterns before release.

Why does my WooCommerce checkout validation fail with custom payment integrations?

WooCommerce checkout validation fails when custom payment integrations lack server-side validation or bypass WooCommerce CRUD APIs. Ensure checkout validation runs server-side for both legacy checkout and Blocks to prevent data processing errors.

What is the best way to review WooCommerce payment gateway code for money-handling errors?

The best way to review WooCommerce payment gateway code is to detect float-based price handling and unsafe cart or session access. Verify secure request handling and safe runtime API usage to prevent financial errors before deployment.

Does my WooCommerce extension need a compatibility declaration for custom order logic?

Your WooCommerce extension needs a truthful feature compatibility declaration if it touches order logic, stock updates, or webhooks. Enforcing WooCommerce CRUD patterns ensures safe runtime use across different storage configurations.

How do I prevent template overrides from breaking WooCommerce subscriptions and bookings?

To prevent template overrides from breaking WooCommerce subscriptions and bookings, review fragile template modifications against standard CRUD patterns. Verify that order and product logic uses storage-agnostic access to avoid runtime failures.