Slash Command

/qa

Systematic QA testing with health scoring — tests web app, finds bugs, fixes them iteratively. Regression mode for re-testing known issues.

Install

npx claudepluginhub shaheerkhawaja/productionos --plugin productionos

Details

Namespacecommands/

Prompt Preview

# /qa — Systematic QA Testing

Test the web app systematically. Find bugs. Fix them. Re-test. Score health 0-100.

## Step 0: Preamble
Run `templates/PREAMBLE.md`. Detect dev server URL.

## Step 1: Discover


## Step 2: Smoke Test
Dispatch `browser-controller` to navigate key pages:
- Home/landing
- Auth (login/signup)
- Dashboard/main
- Settings
- Any page with forms

Report: loads? errors? missing elements?

## Step 3: Deep QA (if mode = full)
Dispatch parallel agents:
- `browser-controller`: Navigate every route, screenshot each
- `ux-auditor`: Full WCAG + interaction audit on each page...

Command Content

Other plugins with /qa

/qa

vbw

/qa

Executes QA engineer workflow: verifies code against requirements using Playwright/pytest/jest, tests boundaries, classifies bugs vs. assumption errors, produces test reports with fix suggestions.

ReadWriteEdit+13

cc-best

/qa

Performs functional QA validation with test evidence and reports on plan paths, PR URLs, or feature descriptions. Supports --autonomy=autopilot|critical|verbose flag.

desplega

/qa

pr-quality/

Runs local QA quality gate on current changes vs base branch (default main), evaluating test coverage, error handling, code quality; outputs verdict (PASS/WARN/CRITICAL_FAIL), summary, findings, and JSON.

sonnetBash(git:*)ReadGrep+3

project-toolkit

/qa

commands/

Senior QA Engineer that creates test plans and executes comprehensive testing including auth flows and edge cases. Trigger on testing, QA, test plan, regression, bug report, or auth flow testing.

navox-agents

/qa

Activate the qa-testing team to collaboratively work on QA and testing tasks

qa-testing

Stats

Stars6

Forks2

Last CommitMar 21, 2026

Actions

View Source View Plugin View on GitHub View README

/qa — Systematic QA Testing

Test the web app systematically. Find bugs. Fix them. Re-test. Score health 0-100.

Step 0: Preamble

Run templates/PREAMBLE.md. Detect dev server URL.

Step 1: Discover

# Detect dev server
curl -s http://localhost:3000 > /dev/null 2>&1 && echo "Dev server: http://localhost:3000"
curl -s http://localhost:8000 > /dev/null 2>&1 && echo "Dev server: http://localhost:8000"

Step 2: Smoke Test

Dispatch browser-controller to navigate key pages:

Home/landing
Auth (login/signup)
Dashboard/main
Settings
Any page with forms

Report: loads? errors? missing elements?

Step 3: Deep QA (if mode = full)

Dispatch parallel agents:

browser-controller: Navigate every route, screenshot each
ux-auditor: Full WCAG + interaction audit on each page
self-evaluator: Score each page's quality

Step 4: Health Score

Calculate 0-100 score:

Pages load without error: 20 pts
No console errors: 15 pts
Forms work: 15 pts
Accessibility passes: 15 pts
Responsive: 15 pts
Performance (< 3s load): 10 pts
No broken links: 10 pts

Step 5: Fix Loop (if fix = on)

For each bug found:

Read the source file causing the issue
Fix with minimal change
Re-test to verify fix
Self-eval the fix quality

Step 6: Report

Write to .productionos/QA-REPORT-{timestamp}.md:

# QA Report
**Health Score:** X/100
**Pages Tested:** N
**Bugs Found:** N
**Bugs Fixed:** N
**Regressions:** N (if regression mode)

Self-Eval

Run templates/SELF-EVAL-PROTOCOL.md on QA thoroughness.