qa

Introduce & guide usage of the qa plugin — which commands, which skills, the automation vs manual workflows, and the platform router

Kill all running Appium servers using the kill-appium.sh script

Review the current git change (diff) against the design system & coding rules, output findings with code + how to fix

Review the ENTIRE codebase against the design system, coding rules and cross-file consistency

Analyze a requirement/spec doc from a QA perspective (testable items, ambiguity, risk, questions for the PO) into an md file used as input for /qa:plan-gen-testcases and /qa:gen-testcases (read-only, no edits)

Read Figma design screens and extract structured UI summary (layout, elements, states). Use when a Figma URL is provided and design context needs to be fetched. Returns structured markdown.

Read a single Lark wiki/docx document and extract structured content (text, tables, comments). Use when a Lark URL is provided and document content needs to be fetched. Returns structured markdown.

Discover elements from live app via Appium MCP, save as elements.json, then create/update Screen classes. Use when elements are unknown or need verification.

Reusable logic acting as a "green gate" — clean compile/build (auto-detects the project's build system) and (optionally) a quick run of the just-touched feature's tests. Use before finishing cook/fix/exploratory and before committing in push-code/merge-request. Do not raise timeouts / add workarounds just to "pass the test".

Reusable logic to commit & push safely — never push directly to main/master (auto-creates a feat/<slug> branch), commit per Conventional Commits with a Co-Authored-By trailer, push -u without force. Used by push-code and merge-request after the code is clean + build is green. Runs only when the user requests it.

Engine that writes mobile test code (Appium Java + TestNG + POM), used by the cook command when the platform is android/ios. Covers 3-layer element lookup, Screen declaration (via the declare-screen skill), writing atomic/flow Tests, TestNG XML (GoToHomeTest first), Utils.passCap/failCap with the [APP-BUG] triage label, build verification, sitemap updates, and recording elements missing an id. Keeps the cook command a thin router.

Reusable logic to write/maintain a Playwright Java Page Object (Screen) + <Feature>Tests class + smoke/regression runner following the 3-layer POM, with correct locator priority and isDisplayed(), and NO assert in the Screen. Used by the cook/plan-tests command (creating a new feature or extending one). Hooks the missing-ids skill for elements lacking data-testid; verifies via the build-verify skill.

Reusable logic to write/update a "Screen" Page Object following the project's POM standard (Appium Java, cross-platform Android/iOS/Flutter). Used when a command (cook, exploratory) needs to declare a screen as a Screen class — @MobileFindBy fields by locator priority, isDisplayed(), verb-style action methods, NO assert. Includes the strategy for choosing stable locators and hooks into the missing-ids skill for elements lacking an id.