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

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…

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…

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…

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…

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…

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…

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…

Provision a disposable Jurassic Ninja store for the Maestro smoke suite, connect Jetpack to the developer's own WordPress.com test account, create WooCommerce API keys, and write .maestro/.env.local. Use when Maestro setup is missing, when .env.local points…

Diagnose and fix Swift strict-concurrency warnings in WooCommerce iOS. Use for Swift 6 migration, actor-isolation changes, and Sendable diagnostics in this repository.

Create a pull request following WooCommerce iOS conventions

Build the WooCommerce iOS project

Render SwiftUI view snapshots for design comparison and visual iteration. Use for layout, styling, or state variants; use verify for navigation and live app behavior.

Run tests for WooCommerce iOS (full suite or targeted)

Verify a requested app flow or changed feature on an iOS simulator with UI evidence. Reuse a suitable session or set up mocks by default.

Log in to a test store on an iOS simulator. Use live-store DEBUG login by default, WireMock when mocks are requested, and the specified store for "my site".

Provision a disposable Jurassic Ninja store for the Maestro smoke suite, connect Jetpack to the developer's own WordPress.com test account, create WooCommerce API keys, and write .maestro/.env.local. Use when Maestro setup is missing, when .env.local points…

Prepare the local environment for the Maestro smoke-test suite — verify tooling, select a device, collect the APK if needed, validate the .env file by variable name only, then hand the user the exact lab-store CLI command to run or run it on request.

Repair a failing WooCommerce Android Maestro flow by reproducing it against the store it runs on, inspecting Maestro selectors, patching the smallest selector/wait/setup issue, and rerunning with repeat evidence. Human-triggered only.

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.

Main app Jetpack Compose UI patterns (WooTheme, Fragment hosting, composeView/legacyComposeView helpers, preview annotations, WC components). Use when writing, editing, exploring, debugging, or reviewing Compose UI in the store management app. NOT for POS…

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.

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

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

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…

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

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

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

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

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…

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

Guidelines for UI text and copy in WooCommerce Fraud Protection. Use when writing user-facing text, labels, buttons, notices, or customer-facing messages.

Build or modify the WooCommerce Fraud Protection admin UI in client/ (React, TypeScript, @wordpress/ui, DataViews, @wordpress/data) and its Jest tests. Use when adding or changing settings pages, lists, drawers, dialogs, stores, hooks, styles, or front-end…

Add or modify WooCommerce Fraud Protection 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.**

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

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

Guidelines for git and GitHub operations in the WooCommerce Fraud Protection repository.

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

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

Use when linting, formatting or checking Google Analytics for WooCommerce code before a commit or push – PHPCS, PHPStan, ESLint, Prettier, the PHP deprecation check, the pre-commit hook or what CI runs. Triggers on "run the linters", "fix lint errors",…

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

Use when asked to create, open or submit a pull request in Google Analytics for WooCommerce, or to push a branch for review. Runs the checks, fills the PR template and the changelog entry, pushes and opens the PR. Triggers on "create a PR", "open a PR", "push…

Use when reviewing a Google Analytics for WooCommerce pull request or local changes. Checks the latest code against the AGENTS.md code rules, backward compatibility, boundaries and the PR's testing instructions. Triggers on "review this PR", "review my…

Use when running Google Analytics for WooCommerce tests – PHPUnit, JS unit tests or Playwright E2E, a full suite, one file or one test – or when setting up the wp-env test site or moving it to another PHP version. Triggers on "run the tests", "run this test",…

Use when starting work on a task or a Linear issue in Google Analytics for WooCommerce and a new branch is needed. Names the branch and creates it from trunk. Triggers on "start a branch", "create a branch for STOMAIL-1234", "start working on this issue". Do…

Use when a Google Analytics for WooCommerce pull request needs a changelog entry, or when deciding whether it needs one. Covers the "### Changelog entry" section of the PR template and the "changelog: none" label. Triggers on "add a changelog entry", "does…

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…

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…

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…

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…

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…

Turn the uncommitted changes into small, isolated commits, one at a time. Stage one unit, suggest a commit message, then wait while the user reviews and commits by hand. Use when the user wants to wrap up a session, split work into commits, or says "stage the…

Write Markdown documentation in alignment with project standards. Always use this skill to create or update .md files.

Draft a standardized, reviewer-focused pull request description and - only after explicit approval - update the PR. Optional arguments are an issue ID (e.g. ABC-123), a base branch for the diff (e.g. dev/develop), and free-text context about the change.

Run a PR readiness check on the current branch before opening or finalizing a pull request. Optional arguments are a base branch name and free-text context about the change (e.g. the issue description).

Make a scope of code self-explanatory: rename unclear symbols, delete comments that restate the code, and untangle clever code that only works with a comment attached. Defaults to all uncommitted changes.

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…

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…

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…

Open a GitHub pull request for the Sensei LMS Certificates plugin the way this repo requires. Use this whenever the user wants to create, open, draft, or "put up" a PR, or says things like "open a PR", "create a pull request", "make a PR for this branch", or…

Verify a Sensei LMS Certificates UI or behavior change end-to-end against the running WordPress site. Use after making a change that affects the certificate template designer, the generated PDF, the "View Certificate" link/block, or any admin/front-end…

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…

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…

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…