woocommerce

Use when the merchant asks how to merchandise the catalogue, which products or categories deserve attention, which products are slow movers, how current stock or sale pricing affects product placement, or which product pages need practical improvements. Produces a merchant-friendly WooCommerce catalogue merchandising review using existing analytics and product tools, with aggregated data only, no customer PII, no forecasts, and no suggestions to build new tools.

Use when the merchant asks which channels, sources, media, campaigns, or devices are driving revenue, customers, or on-hold pipeline. Produces a merchant-friendly WooCommerce channel performance review using existing attribution analytics, with aggregated data only, no customer PII, no ROAS or ad-spend claims, and no suggestions to build new tools.

Use when the merchant asks whether coupons are working, which coupon codes are performing, whether discounting is eating margin, what a promotion cost, which coupons drive new customers, or which codes need attention. Produces a merchant-friendly WooCommerce coupon performance triage using existing analytics tools, with aggregated data only, no customer PII, and no suggestions to build new tools.

Use when the merchant asks how customer acquisition is performing, whether new customers are growing, which channels brought first-time customers, how new customers compare with returning customers, or what practical acquisition actions to take. Produces a merchant-friendly WooCommerce customer acquisition review using existing analytics tools, with aggregated data only, no customer PII, no forecasts, and no suggestions to build new tools.

Use when the merchant asks about customer lifetime value, best customers over time, repeat buyers, one-time versus repeat purchasing, cohort retention, reorder cadence, loyalty opportunities, or whether recent customers are becoming more valuable. Produces a merchant-friendly WooCommerce customer value review using existing analytics tools, with aggregated and pseudonymised data only, no customer PII, and no suggestions to build new tools.

Use when the merchant asks to triage failed orders, on-hold orders, stuck payments, unpaid orders, payment pipeline, checkout failures, payment-gateway problems, or which orders need chasing. Produces a merchant-friendly WooCommerce payment-risk triage using existing analytics tools, with no customer PII and no suggestions to build new tools.

Use when the merchant asks which countries are driving revenue, orders, customers, refunds, or geographic mix changes; whether revenue is concentrated by country; which country-level signals need operational attention; or whether tax-threshold context is relevant. Produces a merchant-friendly WooCommerce billing-country performance review using existing analytics tools, with aggregated data only, no customer PII, no legal or tax advice, and no suggestions to build new tools.

Use when the merchant asks about stock risk, inventory risk, out-of-stock or low-stock products, products to restock or watch, slow-moving stocked products, or sale-priced products with stock issues. Produces a merchant-friendly WooCommerce inventory risk review using existing catalogue and analytics tools, with aggregated data only, no customer PII, no forecasts, and no suggestions to build new tools.

Launch the WooCommerce app on a simulator already authenticated into a given store (site credentials, application password, or WPCom), skipping the manual login UI. Meant to be referenced by other skills/workflows that need a logged-in session fast, but also directly runnable.

Debug a failing test or build error in WooCommerce iOS

Evaluate WooAIAssistant against a structured scenario suite with hard invariants + LLM-as-judge rubric scoring. Runs live against the demo store + gpt-5.1 via the woo-mobile-ai backend wrapper, writes a JSONL run record, compares against stored baselines, and surfaces regressions. Always delegated to a subagent so the main context only sees the markdown report.

Build the app, launch on simulator, and verify feature behavior via mobile-mcp interaction. Use after making changes to visually confirm they work from a user's perspective.

Create a pull request following WooCommerce iOS conventions

Set up the ContextA8C MCP server for accessing Automattic internal resources (Slack, Linear, P2s, GitHub Enterprise, etc.)

Discover and boot an iOS simulator. Use before any command that needs a simulator UDID.

Start or stop the WireMock API mock server for UI testing and E2E verification.

Build, install, and visually verify the app on an Android emulator or device. Uses the Android CLI for agents (android) when available with a full mobile-mcp/adb fallback.

Run the Android AI Assistant headless smoke regression harness without launching UI.

Generate screenshot coverage for screen-level Compose previews from the current diff or a specific target, check required visual and data variations, and produce a compact visual report

Create a pull request following project conventions. Triggers on any request to create, open, make, submit, file, send, push, spin up, put up, draft, raise, or prepare a PR/pull request.

POS analytics tracking patterns (WooPosAnalyticsEvent sealed class, WooPosAnalyticsTracker, WooPosAnalyticsEventConstant). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in POS (WooPos*) code. NOT for main store app — use the `store-analytics` skill instead.

POS unit testing patterns (WooPosCoroutineTestRule, runTest, advanceUntilIdle, mockito-kotlin, event bus mocking, analytics verification). Use when writing, editing, exploring, debugging, or reviewing unit tests for POS (WooPos*) code. NOT for main store app tests — use the `store-tests` skill instead.

Review code changes against project architecture, style, and conventions

Main app analytics tracking patterns (AnalyticsEvent enum, AnalyticsTrackerWrapper, KEY_*/VALUE_* constants). Use when writing, editing, exploring, debugging, or reviewing analytics tracking in the store management app. NOT for POS (WooPos*) code — use the `pos-analytics` skill instead.

Identify performance issues in WooCommerce PHP code. Use when writing or reviewing code that loads collections of post-based objects (products, orders), renders product lists with images, reads multiple options in a loop or method, or writes SQL queries involving joins, aggregates, meta lookups, or range queries.

Commit uncommitted changes with well-crafted messages following WooCommerce repo conventions. Use when the user says "commit", "commit changes", "commit this", "git commit", or "save my work".

Setup and develop the WooCommerce block email editor. Use when working on email templates, transactional emails, or the email editor feature.

Create a high-quality draft PR for the current branch. Use when the user says "create a PR", "draft PR", "open a PR", "make a PR", "push and create PR", or "submit PR".

Set up, start, stop, restart, verify, and troubleshoot the WooCommerce Core local development environment with wp-env and asset build watchers. Use when Codex is asked to run WooCommerce locally, prepare wp-env, watch WooCommerce builds, choose between full and targeted build/watch commands, diagnose localhost:8888, or explain local environment setup commands.

Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.

Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**

Add or modify routes in the WooCommerce Store API (`/wc/store/v1/*`). Use when creating new Store API endpoints, modifying existing ones, or designing the schemas blocks and external integrations consume. Covers authentication, REST URL design, schema/response alignment, variation handling, idempotency, and common pitfalls.

Scans open feature requests for a WooCommerce Marketplace product against its changelog and flags requests whose feature has already shipped. Recommends marking them as completed with a reply pointing to the version. Use when asked to find or close fulfilled/shipped feature requests on WooCommerce.com.

Scans all feature requests for a WooCommerce Marketplace product and surfaces duplicates. Use when asked to find or clean up duplicate feature requests on WooCommerce.com.

Scans open feature requests for a WooCommerce Marketplace product and flags ones that look like spam (promotional links, gibberish, off-topic, copy-pasted SEO content). Lets the user select which to mark as spam, then silently sets the status to spam — no comment is posted. Use when asked to find or clean up spam feature requests on WooCommerce.com.

Scans open feature requests for a WooCommerce Marketplace product and flags stale ones (opened more than 3 years ago with 2 or fewer votes). Groups them semantically, proposes tailored closing comments per group (with workarounds/plugins where known), then closes approved ones. Use when asked to find or clean up stale/old/low-vote feature requests on WooCommerce.com.

Scans open feature requests for a WooCommerce Marketplace product and flags ones that are actually support questions (troubleshooting, setup help, bug reports framed as features). Lets the user select which to close, then posts a closing comment redirecting them to woocommerce.com/contact-us/. Use when asked to find or clean up support questions misfiled as feature requests.

Full triage orchestrator for a WooCommerce Marketplace product's feature requests. Fetches all requests once to disk, then delegates each phase (completed → duplicates → spam → support → stale) to a subagent to keep the main context light. State is persisted under `.triage-state/<product_id>/` so the run is resumable per-FR. Ends with an optional free-form analysis pass. Use when asked to run a full triage or cleanup on a product's feature requests.

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.

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).

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).

Reviews code changes for quality, security, and adherence to project standards. Use when reviewing PRs, commits, or staged changes.

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.

Build and publish a GitHub Release for the WooCommerce Fraud Protection plugin. Use when creating a new release.

Run tests, linting, and quality checks for WooCommerce development. Use when running tests, fixing code style, or following the development workflow.

Review WooCommerce code changes for coding standards compliance. Use when reviewing code locally, performing automated PR reviews, or checking code quality.

Guidelines for git and GitHub operations in the WooCommerce repository.

Guidelines for creating and modifying markdown files in WooCommerce. Use when writing documentation, README files, or any markdown content.

Use when adding or editing changelog entries for this plugin. Triggers include "add changelog", "changelog entry", "release notes", "update changelog.txt", "update readme.txt", or any PR that introduces user-visible behavior changes. Critical: changelog.txt and readme.txt use different version-header formats and must both be updated.

Use when adding a new payment method to the Stripe gateway. Triggers include "add payment method", "new UPE method", "support <method-name> on checkout", "register a payment method", or any work that introduces a new `WC_Stripe_UPE_Payment_Method` subclass. A new method spans PHP and frontend plus constants and registration; this skill walks the full sequence so nothing is silently missing on checkout.

Use when PHPStan reports new errors and you're considering whether to fix them or baseline them. Triggers include "PHPStan errors", "phpstan baseline", "level 8 errors", "fix phpstan", "phpstan-baseline.neon". Project policy is fix-first, baseline-last; this skill enforces that triage order.

Use when a new WooCommerce beta or release candidate is available and you need to test the plugin's compatibility. Triggers on phrases like "test against WC beta", "compatibility test", "new WooCommerce version".

QIT (Quality Insights Toolkit) expert for WooCommerce extension testing. Use when working with QIT commands, test packages, E2E tests, managed tests, debugging test failures, environment management, qit.json configuration, WooCommerce quality testing, or anything related to qit run:*, qit env:*, qit package:* commands.

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.