# Bugsweep

> Use when asked to QA an app end to end, run a full-path / 전체 경로 / 전수 QA, capture screenshots of every screen, or verify all user flows (signup, login, every feature) of a locally runnable web, iOS, Android, API, or monorepo project. Triggers on "전수 QA", "모든 화면 캡쳐", "직접 써보고 버그 찾아줘", "full QA pass".

- Skill: `testbeagle/bugsweep` (Agent Skill)
- Install (CLI): `npx skillmds@latest add testbeagle/bugsweep`
- Raw SKILL.md: https://api.skillmd.com/api/skills/testbeagle/bugsweep/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: TestBeagle (https://skillmd.com/u/testbeagle)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/testbeagle/bugsweep

---


# bugsweep

Plan-gated, full-path functional QA: run the app locally, walk every user path from signup/login through every feature, capture each screen, exercise the flows, and report with evidence. Never claims a pass it didn't verify.

## Phase 0 — Discover (reuse preflight)

Run `preflight` (or reuse its report). Get: targets, run commands, readiness method, seed/review tooling, output location, drivers. If a target isn't locally testable, say so and don't fake it.

## Phase 1 — Route map + approval gate (MANDATORY — stop here)

Build the full route map: for every path from signup/login onward — **경로 + 상태** (logged-out/in, empty/populated), **변형** (dark mode, locales), **드라이버** per route (`../beagle-shared/drivers-web.md` / `../beagle-shared/drivers-mobile.md`), and **검증 불가 예정** + 이유 (e.g. simctl can't tap; no interactive web driver → capture-only). Then present it and stop per the shared gate in **`../beagle-shared/approval-gate.md`** — nothing launches, seeds, or captures until the user approves.

## Phase 2 — Launch

Start services with the discovered commands. Confirm readiness by **evidence** (poll the health endpoint; grep the build log for the success marker) — never by exit code alone. Run the seed script if one exists.

## Phase 3 — Capture & QA every route

- Static screens: prefer the repo's native capture scripts / review-mode deep links; else drive the real UI.
- Flows: actually perform signup, login, navigation, CRUD — **where the driver supports interaction**. With capture-only headless Chrome (no agent-browser, no browser MCP, no repo E2E tool), you get screenshots but not driven flows: put those flows in 검증 불가.
- Web with an interactive driver: after **every** route check console, page errors, and network (`agent-browser console` / `errors` / `network requests`, or the MCP's `list_console_messages` / `list_network_requests`) — errors are findings. With capture-only headless Chrome, console/network aren't captured — record that as 검증 불가 unless the repo's own tooling provides them.
- API targets (no UI): don't screenshot — hit each endpoint (curl/httpie), check status, schema, and error handling; report coverage as an endpoint table.
- Capture every screen × state × variant in the approved map (screenshots, and video for flows where useful).

## Phase 4 — Report

Write per `../beagle-shared/report-base.md` (Korean default, anti-slop rules enforced). Finding fields: the common block plus, per finding, the exact reproduction and the console/network/screenshot evidence. Everything you couldn't exercise goes in 검증 불가.

## Phase 5 — Offer a static runner

Offer to freeze the capture flow into a repo-native `.sh` (via `../beagle-shared/emit-runner.md`, the `scriptify` mechanism) so future runs need no agent. Don't auto-commit — offer it.

## Hard rules

- Android: launch with `am start -n`, **never `adb monkey`** (it clears the rotation lock). Uninstall before install — never `install -r` (stale build).
- iOS: a build wrapper's exit 0 is meaningless — confirm `BUILD SUCCEEDED` in the log.
- Any tap/flow/state you can't verify goes in 검증 불가 with the reason. Never silently skip, never fake a pass.