statuslisted

Print a one-shot health + inventory snapshot of the QA catalog in this project — browser-agent install status, catalog framework/route/task counts, configured issue-tracker integrations, drift vs. source, and the most recent run's pass/fail/blocked totals. Read-only; never modifies the catalog. Use to verify an install or get your bearings before a run.
elwizard33/qa-my-app · ★ 1 · Testing & QA · score 67

Install: claude install-skill elwizard33/qa-my-app

# /qa-my-app:status — Catalog health & inventory ## Snapshot - Inventory: !`node "${CLAUDE_PLUGIN_ROOT}/scripts/status.mjs"` - Drift vs. source: !`node "${CLAUDE_PLUGIN_ROOT}/scripts/catalog-diff.mjs" --notify` ## Instructions This skill is **read-only** — it never writes to `QA-tests/`. Present the two snapshots above to the user as a concise status report, then suggest the single most relevant next command: - If the browser agents are missing **or** `QA-tests/catalog.json` is absent → recommend `/qa-my-app:init`. - If drift was reported (`⚠ N route(s) drifted`) → recommend `/qa-my-app:sync`. - If a per-role credential is unresolved (the snapshot shows `✗ <role>: … missing <ENV_VAR>`) → tell the user to export that env var (or fill `auth.local.json`) before running that role's protected tasks. - If the catalog is present and up to date but there's no last run → recommend `/qa-my-app:run-all` (or `/qa-my-app:run <task>` for a single task). - If everything is current and a recent run exists → report the pass/fail/blocked totals and note the catalog is healthy; no action needed. Do not spawn subagents and do not run a browser. Keep the report to what the two snapshot commands returned.