verifylisted
Install: claude install-skill sjzavala/claude-qa-tms
# Verify a test case in the browser
Input: **$ARGUMENTS** — one or more case IDs in `<PROJECT>-<n>` form, exactly as Qase displays them (e.g. `ACME-42`, or `ACME-42 ACME-43`). If empty, ask which case, or offer the list from `qql_search`.
## Step 1 — Resolve each ID, then fetch the case
Split each argument on the **last** hyphen. The left side is the project `code`, the right side is the numeric `id` — `qase_get` takes them as two separate params and will not accept the combined string.
| Argument | `code` | `id` |
|---|---|---|
| `<PROJECT>-<n>` | `"<PROJECT>"` | `<n>` |
| e.g. `ACME-42` | `"ACME"` | `42` |
Then `qase_get` with `{entity: "case", code: "<PROJECT>", id: <n>}` per ID. Pass `id` as a **number** — not a quoted string, and never the whole `"<PROJECT>-<n>"` combined form.
Take the project code from the argument itself, not from anything hardcoded here — the examples above are illustrative only.
If an argument is a bare number there is no project code in it. Use the project code already established in this conversation if there is exactly one; otherwise ask rather than guessing.
**Echo what you fetched before executing anything:** one line per case — `<PROJECT>-<n> → "<case title>" (N steps)`. If the title doesn't look like the case the user meant, stop and say so. Silently verifying the wrong case is worse than asking.
Tool names and params: `references/qase-tools.md`. The published Qase README lists names that don't exist on the shipped server — trust tha