Stats
Actions
Available In
Tags
Plugin
qa-operator
Delegated browser QA operator: plan, run, monitor, triage, and optionally repair acceptance checks from requirements with evidence dashboards.
What's Inside
Skills6
monitor
/monitor
Serve or open the qa-operator live dashboard. Use when the user wants to monitor QA progress, see a dashboard, watch run status, view screenshots as they appear, or continue an existing QA dashboard; triggers include "monitor 켜줘", "대시보드 열어줘", "진행상황 보여줘", "QA dashboard", "live monitor", "실시간으로 보고싶어". Reads manifest.json, qa-plan.json, and runs/latest or latestRun qa-results.json; writes no QA results.
plan
/plan
Convert requirements into a qa-operator plan. Use when the user provides a spreadsheet, issue list, PR, current diff, feature checklist, staging URL, or range and wants browser QA planned before execution; triggers include "QA 계획", "qa-plan.json", "요구사항 정리", "시트 범위 QA", "테스트 케이스로 바꿔줘", "plan QA", "acceptance plan". Writes artifacts/qa-operator/SLUG/qa-plan.json, manifest.json, index.html, and an initialized run skeleton. Do not use when the user only wants to run an already existing plan.
repair
/repair
Fix scoped, verifiable local defects found by qa-operator and rerun affected QA items. Use when the user explicitly allows repair, asks to "고치고 재검증", "명백한 버그는 수정", "auto repair local bugs", "fix failed QA", or "repair and retest". May modify application code only for narrow defects, writes repair-log.md, updates qa-results.json, and reruns affected items. Do not use for product decisions, production writes, destructive data actions, broad redesign, or ambiguous UX preferences.
run
/run
Execute browser QA from an existing qa-plan.json and update evidence incrementally. Use when the user wants server access, login, feature checks, validation, screenshots, traces, console/network logs, UI/UX risk scanning, or retry of failed items; triggers include "브라우저로 QA 실행", "직접 확인해줘", "QA run", "실행하면서 결과 업데이트", "스크린샷 남겨줘", "FAIL만 재검증", "run browser QA". Writes only runs/RUN_ID/qa-results.json, screenshots, traces, logs, and summary files under artifacts/qa-operator/SLUG/ unless paired with repair.
start
/start
Default delegated QA entry for qa-operator. Use when the user wants to hand off QA from a requirement source, spreadsheet, issue, PR, feature list, current diff, or staging URL; triggers include "QA 맡겨줘", "완전 QA 돌려줘", "브라우저로 직접 확인해줘", "제대로 구현됐는지 확인해줘", "UI/UX 문제까지 찾아줘", "monitor 켜고 진행상황 보여줘", "실패 항목 재검증해줘", "run QA", "browser QA", "delegated QA". Writes a qa-operator artifact tree under artifacts/qa-operator/SLUG/ and routes to plan, monitor, run, triage, and optional repair. Do not use for pure code review with no browser or acceptance evidence requirement.
Stats
Version0.1.0
LanguageJavaScript
Stars1
MaintenanceGood
Last Commit
Added
Available In
Tags
Categories
