One prompt. Three agents. A full QA report.

AI-powered QA that analyzes your codebase with parallel agents and produces a browsable dashboard β€” findings, screenshots, videos, fix lists and Jira-ready tickets.

agents 3 parallel dashboard Docsify evidence screens + video output Jira Β· Confluence
$ npx qa-toolkit-ai init

01The flow

Install the skills into your project's .cursor/, say one word, and watch three agents sweep the codebase in parallel.

cursor
you: /qa

  β–Έ qa-frontend  scanning components, a11y, responsive…  done
  β–Έ qa-backend   scanning API, validation, errors…      done
  β–Έ qa-e2e       driving the site, capturing video…     done

  QA REPORT
  ─────────
  findings: 3 critical Β· 11 major Β· 24 minor
  evidence: 18 screenshots Β· 4 E2E videos
  split:    functional (PM) vs technical (devs)

  βœ“ dashboard  docs/qa-dashboard (Docsify)
  βœ“ fix list   prioritized, effort-estimated
  βœ“ tickets    Jira-ready markdown
  βœ“ share      public link via cloudflare tunnel

02What you get

β—† Three parallel agents

Frontend, backend and E2E agents run at the same time, each with its own checklist and report format.

β—† Browsable dashboard

Every finding lands in a Docsify site β€” filterable, organized, and easy to scroll in a review meeting.

β—† Functional vs technical

Findings split into a PM/client view and a developer view. Nobody reads what they don't need.

β—† Evidence built in

Screenshots at desktop, tablet and mobile widths, plus E2E videos of actual broken flows.

β—† Tickets & checklists

Generates Jira-ready tickets and Confluence checklists from the findings. Paste and assign.

β—† Shareable link

A Cloudflare tunnel exposes the dashboard publicly, so stakeholders without repo access can browse it.

03Commands

Run everything, or aim at one layer.

CommandWhat it runs
/qaFull sweep β€” all three agents + merged report
/qa-frontendComponents, accessibility, responsive behavior
/qa-backendAPI contracts, validation, error handling
/qa-e2eReal user flows, captured on video
npx qa-toolkit-ai initInstall skills, rules and dashboard template into .cursor/

04Why it exists

The decisions worth knowing about, written down.

QA findings die in chat history

An agent that says "looks mostly fine" in a chat window is useless a week later. The dashboard makes findings a durable artifact.

Evidence beats opinion

Every finding ships with a screenshot or video of the actual breakage. No "works on my machine" arguments.

Two audiences, one run

PMs get functional impact, devs get stack traces and file paths β€” from the same analysis, without a second pass.