woocommerce/woocommerce-android

setup-test-stores

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…

Langue du texte source : anglais

smoke-tests

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.

Langue du texte source : anglais

maestro-flow-doctor

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.

Langue du texte source : anglais

verify-on-device

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.

Langue du texte source : anglais

store-compose

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…

Langue du texte source : anglais

pr

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.

Langue du texte source : anglais

woo-ai-smoke

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

Langue du texte source : anglais

ui-review

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

Langue du texte source : anglais

pos-analytics

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…

Langue du texte source : anglais

pos-tests

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…

Langue du texte source : anglais

review

Review code changes against project architecture, style, and conventions

Langue du texte source : anglais

store-analytics

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…

Langue du texte source : anglais

store-tests

Main app unit testing patterns (BaseUnitTest, BDD naming, mockito-kotlin, AssertJ, StateFlow/LiveData capture, coroutine dispatchers). Use when writing, editing, exploring, debugging, or reviewing unit tests in the store management app. For POS (WooPos*)…

Langue du texte source : anglais

store-viewmodel

Main app ViewModel patterns (ScopedViewModel, Hilt, StateFlow, triggerEvent, navArgs, savedState flows, events). Use when writing, editing, exploring, debugging, or reviewing ViewModels in the store management app. Covers navArgs, combine+asLiveData, sealed…

Langue du texte source : anglais

pos

POS (Point of Sale) architecture and patterns. Use when writing, editing, exploring, debugging, fixing bugs, implementing features, or reviewing WooPos-prefixed classes or files under ui/woopos/. POS uses a different architecture than the main app — plain…

Langue du texte source : anglais

pr-feedback

Address PR reviewer feedback by evaluating comments, proposing fixes, and executing after user approval. Use when the user wants to handle review comments on an existing PR, address PR feedback, fix PR comments, respond to reviewer suggestions, or process…

Langue du texte source : anglais