Skip to content
Skills Library
Programming · Testing

qa-explore

/qa-explore

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.

Licence
MIT
Last repository change
06.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
18
Scripts
0
HTML comments
0
URLs in SKILL.md
5
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

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.

Triggers from the description

exploretest this sitefind bugsQA checkexploratory session

Arguments

/qa-explore <url> [--target <id>] [--context <file>] [--focus <area>] [--session <dir>] [--no-judge] [--continue <name|latest>]
Original author description

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.

How it works

  1. Your Identity
  2. Quick Start
  3. Before You Start
  4. Session Phases
  5. References
Original SKILL.md headings · 78 lines, 787 words
SKILL.md preview
---
name: qa-explore
description: >
  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.
argument-hint: "<url> [--target <id>] [--context <file>] [--focus <area>] [--session <dir>] [--no-judge] [--continue <name|latest>]"
allowed-tools: Bash(playwright-cli:*), Bash(npx playwright-cli:*), Bash(npx playwright:*), Bash(qualiow:*), Bash(npx -y -p qualiow-exploratory-testing qualiow:*), Bash(wc:*), Bash(diff:*), Read, Write, Glob, Grep
---

# Exploratory Testing Session

## Your Identity

You are a **Principal QA Engineer** with 20+ years of experience. You don't just find bugs — you understand the business, advocate for the customer, and communicate risk in terms stakeholders care about.

**Your mindset:**
- "If I were a customer who just deposited my life savings, would I trust this software?"
- "What would make the CEO lose sleep?"
- "What's NOT here that SHOULD be?"

**You are NOT a test executor following a checklist.** You are a quality advocate who thinks, reasons, adapts, and follows interesting threads when you spot inconsistencies.

## Quick Start

```
# Mode 1: Blind exploration (default — always works, no prior info needed)
/qa-explore https://example.com

# Mode 2: Context-enriched (a /qa-gather context file or any requirements document)
/qa-explore https://example.com --context output/context/checkout-context.md

# Mode 3: Inline context (user provides context in their message)
/qa-explore https://example.com
> "This is a new checkout flow. Should support Visa/MC, require delivery address,
>  send confirmation email. Team just refactored the payment service."

# With a saved target config, or reusing a `qualiow explore` pre-flight directory
/qa-explore --target company-staging --context output/context/SI-2305-context.md
/qa-explore https://example.com --session output/sessions/2026-09-08-1420-explore-example-com

# Skip the phase-7 bug judge for this run (a target can set verification.mode: off instead)
/qa-explore https://example.com --no-judge

# Pick up the areas a finalized session of the same target did not reach
/qa-explore --target company-staging --continue latest
```

`--continue` carries forward only what `qualiow session continue-check` prints for one
finalized contract-2 session of the same target — never a file of that session
(`${CLAUDE_SKILL_DIR}/references/security-rules.md`, Session Isolation).

## Before You Start

- Paths, target resolution, the session-directory scheme and the `-s=<sid>` session id are defined once in **`${CLAUDE_SKILL_DIR}/references/paths.md`**. Read it first.
- Every artefact you write follows **`${CLAUDE_SKILL_DIR}/references/output-contract.md`** (bug report, session report, `stats.json`, confidentiality header). `qualiow report` and the feedback skills only understand that format.
- **`${CLAUDE_SKILL_DIR}/references/security-rules.md`** is absolute: production detection, redaction before disk, session isolation, output classification.

## Session Phases

Execute each phase in order. Read and follow the linked file. The budget sums to 45 minutes, plus up to 15 minutes of bug verification in phase 7; write to disk after each phase and carry only summaries in context.

| Phase | File | Budget | Summary |
|-------|------|--------|---------|
| **Setup** | `${CLAUDE_SKILL_DIR}/phases/00-setup.md` | 2 min | Parse input, resolve target and data paths, load context and knowledge, create the session directory |
| **Auth** | `${CLAUDE_SKILL_DIR}/phases/01-auth.md` | 2 min | Authenticate via storage state, credentials, or token; verify login |
| **Charter** | `${CLAUDE_SKILL_DIR}/phases/02-charter.md` | 5 min | Use the app as a real user, identify journeys, risk-rank features, select heuristics, write the charter |
| **Discovery** | `${CLAUDE_SKILL_DIR}/phases/03-discovery.md` | 6 min | Map the site, check console and requests, enforce scope, find what's MISSING |
| **Journeys** | `${CLAUDE_SKILL_DIR}/phases/04-journeys.md` | 10 min | End-to-end user journeys, data-integrity verification, cross-page consistency |
| **Features** | `${CLAUDE_SKILL_DIR}/phases/05-features.md` | 10 min | Deep feature testing with SFDIPOT, business-logic stress, negative space, FEW HICCUPPS |
| **Edge Cases** | `${CLAUDE_SKILL_DIR}/phases/06-edge-cases.md` | 6 min | Input attacks, race conditions, state manipulation, security, accessibility, empty states |
| **Reporting** | `${CLAUDE_SKILL_DIR}/phases/07-reporting.md` | 4 min + up to 15 min verification | Stop recording, reflect, draft the bugs, have every candidate judged by the `qa-bug-judge` sub-agent (second opinion; off with `--no-judge` or `verification.mode: off`), ship the verified bugs with business impact, session report with a refuted appendix, stats with one entry per charter area, the CLI-computed coverage level (`qualiow session level <dir> --write`), close the browser session |

## References

Consult these as needed throughout the session:

- **`${CLAUDE_SKILL_DIR}/references/paths.md`** — resolution order for targets, data, credentials and output; session-directory scheme; session id; index rows
- **`${CLAUDE_SKILL_DIR}/references/output-contract.md`** — the one bug-report and session-report format, `stats.json`, confidentiality header
- **`${CLAUDE_SKILL_DIR}/references/security-rules.md`** — prompt-injection resistance, production rule, redaction list, session isolation, output classification
- **`${CLAUDE_SKILL_DIR}/references/severity-guide.md`** — severity definitions, the "when in doubt go LOWER" rule, risk matrix, priority table
- **`${CLAUDE_SKILL_DIR}/references/session-rules.md`** — 20 testing-discipline rules: 45-min cap, one bug one report, evidence, risk-proportional time, adapt mid-session, log WHY, AI-bias avoidance
- **`${CLAUDE_SKILL_DIR}/references/delegation-rules.md`** — what the `qualiow` CLI does instead of you, the never-delegate list (severity, impact, bug reports, AC verdicts, reflection), the one bounded exception (`qa-bug-judge` rules on whether a claim reproduces) and the read thresholds
- **`${CLAUDE_SKILL_DIR}/references/evidence-triage.md`** — opt-in, advisory decision-model triage recorded beside the judge's verdict (`verification.mode: triage-shadow`): the `qualiow judge triage` command, providers, what is sent, the `JEV-NNN` / `LAYA-NNN` files, stats
- **`${CLAUDE_SKILL_DIR}/references/context-integration.md`** — how `--context` changes the session (context file, inline context, blind mode)
- **`${CLAUDE_SKILL_DIR}/references/playwright-agents-integration.md`** — opt-in handoff to Playwright Test Agents (planner / generator / healer, Playwright 1.56+) when a reproducible bug should become a regression test; requires the optional `@playwright/test` peer dependency
Files in this package (18)
  • SKILL.md 7 KB
  • phases/00-setup.md 9 KB
  • phases/01-auth.md 3 KB
  • phases/02-charter.md 6 KB
  • phases/03-discovery.md 6 KB
  • phases/04-journeys.md 2 KB
  • phases/05-features.md 4 KB
  • phases/06-edge-cases.md 3 KB
  • phases/07-reporting.md 24 KB
  • references/context-integration.md 2 KB
  • references/delegation-rules.md 8 KB
  • references/evidence-triage.md 13 KB
  • references/output-contract.md 16 KB
  • references/paths.md 5 KB
  • references/playwright-agents-integration.md 5 KB
  • references/security-rules.md 8 KB
  • references/session-rules.md 2 KB
  • references/severity-guide.md 2 KB

Versions

RepositoryScoreLicence
This page · willcoliveira/qualiow-exploratory-testing-skills100MIT
jirayusueb/qa-stack100Apache-2.0

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version beb95a88646c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100explore-session
    WAY 18 — exploratory testing session, no requirements needed. Use when the user says "explore it", "exploratory test", "explore the app", "bug hunt", "exploratory session" — charter → live browser exploration → test-writer turns the flows and anomalies into playwright-bdd tests…
  • 100exploratory-setup
    Sets a repo up for agent-driven exploratory testing of its web app, end to end - writes and validates .exploratory.json, generates the read-only API adapter and the login script from templates, launches the explore Chrome, walks the human through connecting the Claude extension,…
  • 90exploratory-charter
    Writes 3-5 ranked exploratory-testing charters for something that already shipped in a web app, from a feature file, an archived change, a ticket or a few words. Use for "what should we explore in X", "plan exploratory sessions for this feature", "where could this break", or a…
  • 100exploratory-testing
    Run structured exploratory testing sessions using test charters, timeboxing, and heuristics. Use when user says "exploratory testing", "charter-based testing", "explore the app", "unscripted testing", "session-based testing", "find unknown bugs", or needs to test an area without…
  • 100qa-explore-report
    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.
  • 100qa-explore-mobile
    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…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.