메뉴
Generate, regenerate, or reformat reports from existing exploratory testing sessions. Use when user says: "show report", "generate report", "reformat bugs", "session summary", or wants to review past session findings.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Run a full AI-driven exploratory testing session on a simulator/emulator — works for BOTH a NATIVE app (the installed app is the system under test) and a WEB app loaded in the real device browser (iOS Simulator Safari / Android emulator Chrome). The mode is selected from the target config. Same Principal-QA mindset as /qa-explore, but the driver is Maestro (via the mobile-cli shim) instead of Playwright, and the phases are adapted for mobile concerns (app/browser lifecycle, rotation, on-screen keyboard, deep links, offline, permissions, native a11y tree). Use when user says: "test on the simulator/emulator", "explore the app on iOS/Android", "find bugs on mobile", "QA the mobile build", or provides a mobile-sim target (native or web).
Quick focused exploratory testing session on a single page or feature (~15 min). No full site mapping — goes directly to the target, applies heuristics, reports findings. Use when user says: "quick check", "test this page", "quick explore", or wants a fast review.
Run a full AI-driven exploratory testing session against a web application. Acts as a Principal QA Engineer — understands the business first, risk-ranks features, tests end-to-end user journeys, verifies data integrity, finds what's MISSING, and writes bug reports that executives act on. Use when user says: "explore", "test this site", "find bugs", "QA check", "exploratory session", or provides a URL to test.
Interactive setup for a new target application. Navigates to the URL, detects auth requirements, walks through login flow creation, auto-detects scope, and saves target config. Use when user says: "setup target", "add target", "configure app", "new target".
Quick focused exploratory testing session on a single page or feature (~15 min). No full site mapping — goes directly to the target, applies heuristics, reports findings. Use when user says: "quick check", "test this page", "quick explore", or wants a fast review.
Run a full AI-driven exploratory testing session against a web application. Acts as a Principal QA Engineer — understands the business first, risk-ranks features, tests end-to-end user journeys, verifies data integrity, finds what's MISSING, and writes bug reports that executives act on. Use when user says: "explore", "test this site", "find bugs", "QA check", "exploratory session", or provides a URL to test.
| name | qa-explore-report |
| description | Generate, regenerate, or reformat reports from existing exploratory testing sessions. Use when user says: "show report", "generate report", "reformat bugs", "session summary", or wants to review past session findings. |
| allowed-tools | Read, Write, Glob, Grep |
# If "latest" or no session specified:
Read output/sessions/INDEX.md → find most recent session
# If specific session:
Read output/sessions/<session-dir>/
Read all phase files from the session directory:
charter.md — session charterphase-1-discovery.md — discovery findingsphase-2-functional.md — functional testing findingsphase-3-edge-cases.md — edge case findingssession-log.md — full session logbugs/BUG-*.md — all bug reportscoverage-map.md — coverage dataBased on requested format:
markdown (default): Full session report following data/templates/session-report.md
summary: Brief executive summary
bugs-only: Just the bug list
Save to output/sessions/<session-dir>/session-report.md (or specified filename).
Present to user.