Skip to main content

/gws-qa-generate

Generate QA test cases for what the current branch changed. Type /gws-qa-generate inside your AI agent and it reads the branch diff (vs. the default branch), works out which user-reachable flows those changes touch, writes focused test cases, and seeds them to GetWebStack so you can review and edit them in the dashboard before running.

This is the first half of the Branch QA Report loop. Generation and execution are deliberately separate skills, because the point is that a human reviews and edits the cases in between — you own what gets tested. Run /gws-qa-run once you're happy with the cases.

When to use it​

  • You (or an agent) just finished a branch and want QA cases that prove this branch's changes work before merge
  • You want a first draft of test cases you can edit, rather than writing them from scratch
  • You have a spec .md on the branch and want the cases to become the contract the implementation must pass

What it does​

  1. Reads the branch diff — compares the current branch against the default branch to find what actually changed.
  2. Maps changes to flows — figures out which user-reachable flows (pages, endpoints, jobs) the diff touches. The diff is the generation scope — it doesn't re-test the whole app.
  3. Grounds each case in intent — pulls the branch's intent (spec docs on the branch, PR/ticket acceptance criteria, commit messages) to sharpen each case's pass/fail oracle where available.
  4. Synthesizes test cases — writes focused cases that exercise the changed behaviour.
  5. Seeds them to GetWebStack — the API is the canonical store, so the cases show up in the dashboard for you to review, edit, add, or remove.

Two modes (picked automatically)​

The skill decides the mode itself — there's no flag:

  • Diff mode (default) — the branch changes user-testable code. The diff is the scope; intent sharpens each case.
  • Spec-first mode — the diff has no user-testable code change but does contain a spec .md (spec written before the implementation). The generated cases become the contract the implementation must later satisfy.

After generation​

Review and edit the cases in the GetWebStack dashboard, then run them:

/gws-qa-run

See also​

  • /gws-qa-run — run the generated cases in parallel and publish the report
  • Branch QA Report — the end-to-end use case
  • gws qa — the underlying CLI that syncs cases and runs with the API