Site Bug Hunt

Site bug hunt (debbie.codes)

Exploratory QA for this Nuxt Content site. Find and document user-impacting bugs. Do not change product code (use site-bugfix for that).

Quick start (local)

Copy one of these prompts:

Run the site-bug-hunt skill against https://debbie.codes (production).
Write candidates under qa/bug-candidates/. Do not file GitHub issues.

Run the site-bug-hunt skill against http://127.0.0.1:8000 (start npm run dev if needed).
Write candidates under qa/bug-candidates/. Do not file GitHub issues.

Run site-bug-hunt on production and file GitHub issues for high-confidence major/blocker bugs only.

Modes

Also treat an explicit user request to “file issues” like CI filing rules (even in interactive mode).

Tooling

Prefer playwright-cli (see the playwright-cli skill). Use accessibility snapshots as primary evidence.

Optional: Playwright MCP or Chrome DevTools MCP if already configured — keep reports consistent.

Targets

Confirm the target at the start of the report.

Env overrides:

• SITE_BUG_HUNT_BASE_URL — force base URL
• SITE_BUG_HUNT_MODE=ci — enable issue filing
• SITE_BUG_HUNT_ALLOW_MINOR=1 — allow filing minor in CI (default: major/blocker only)
• SITE_BUG_HUNT_MAX_ISSUES — max issues to file (default 3)

Honesty gates (mandatory)

Read references/honesty.md before filing anything.

CI / “file issues” may create a GitHub issue only when all are true:

1. classification=bug
2. confidence=high
3. Severity is blocker or major (or minor if SITE_BUG_HUNT_ALLOW_MINOR=1)
4. Reproduced in this run
5. No open issue already contains the same fingerprint:
6. Under the max-issues cap for this run

Otherwise: write a local candidate and/or mark inconclusive — do not file.

Priority journeys

Read references/journeys.md. Cover at least (unless the user scopes a subset):

1. Home — hero, featured content, awards, recent sections
2. Blog — index, search, filters/tags/year, open a post
3. Videos / podcasts / courses — listing + open an item
4. About + nav (desktop + one mobile viewport)
5. Color mode toggle
6. 404 / unknown route

Gentle crawl (be a good neighbor)

• Prefer the journey list over exhaustive crawling
• Max ~25 page navigations per run unless the user asks for deeper coverage
• Short pause between heavy navigations when hitting production
• Do not submit forms or spam external networks beyond normal browsing
• Check outbound link liveness sparingly (HEAD), not every link on every page

Workflow

1. Pick target and mode; state them in the summary.
2. Open the site with playwright-cli.
3. Explore priority journeys.
4. For each suspected bug, classify per honesty.md and fill the candidate template.
5. Write qa/bug-candidates/<slug>.md (always, for traceability).
6. If CI / file-issues mode and the finding is eligible:
   • Dedupe: gh issue list --state open --search "fingerprint: <value>" (or search body)
   • Create: gh issue create --title "…" --label "bug,agent-hunt,severity:<level>" --body-file …
   • Include structured frontmatter in the issue body
7. Summarize in chat / job summary: candidates, filed issues, skipped (with reasons).

Rules

• Do not invent bugs. Prefer inconclusive over a guess.
• Do not mutate product code or content during a hunt.
• Do not flood issues: respect caps and severity filters.
• Existing specs under tests/ are hints for what already matters — look for gaps.

Done means

• Priority journeys touched (or user-scoped subset)
• Zero or more files in qa/bug-candidates/
• In CI: zero or more high-signal issues filed (or a clear “nothing to file” summary)