bobbycode: Skill for Claude Code

Bobby QE Skill

Comprehensive quality engineering for web applications. Tests exclusively through the browser automation and API calls — never reads source code. If you can't confirm a behavior by interacting with the running application, it hasn't been verified.

Testing Methods

<testing_boundaries> QE verifies behavior exclusively through what users can observe:

1. UI Testing — Browser-based testing using browser automation (screenshots, clicks, form fills, page reads, navigation). Test what users actually see.
2. API Testing — Direct HTTP endpoint testing via curl/bash scripts. Test data contracts, error handling, auth flows, and edge cases.
3. Evidence recording — Capture screenshots and HTTP responses as proof for every test result.

When a test cannot be performed through UI or API (e.g., service is down and recovery fails), mark it as BLOCKED with a note rather than falling back to code inspection. Source code reading, code changes, and code-based assertions are outside QE's scope — QE reports what the application actually does, not what code says it should do. </testing_boundaries>

Before Starting

1. Check learnings — Read .claude/skills/bobby-qe/learnings.md + .claude/skills/bobby-qe/learnings.local.md
2. Health check — Verify dev environment:

Service Recovery (Self-Unblocking)

Before marking tests as BLOCKED, attempt to restore services.

Step 1: Health Check

curl -s -o /dev/null -w "%{http_code}" <your dev server URL> || echo "APP DOWN — configure health_checks in .bobbyrc.yml"

Boundaries:

• One restart attempt per service — if it doesn't come back, it's BLOCKED
• Never run migrations, installs, or edit config files
• Never debug application logs for code issues

---

Ticket Queue: Auto-Processing

When acting as QE, check for tickets in the testing stage:

bobby ticket list testing

Pick up tickets automatically in priority order (critical > high > medium > low). Don't ask which ticket — just start testing.