Pre-Ship App Walkthrough and Bug Report
Walk through real app flows, probe failure states, and deliver prioritized bugs with reproducible steps and visual evidence.
Before & after
Same prompt, same agent — the only difference is the skill.
Pre-ship testing is important. Here's how you might approach a manual walkthrough: - Go through each major user flow - Note any bugs, broken links, or confusing UX - Test on different screen sizes - Check the console for errors - Prioritize issues by severity You could also set up automated end-to-end tests with a tool like Playwright to catch regressions automatically. If you describe your app's main flows, I can help you build a testing checklist. What are the key flows you want to verify?
Walking the built app page by page via the browser CLI — actually
navigating it, not reviewing code. Here's what a run produces.
WHAT IT DOES
Navigates the app like a user, page by page, capturing bugs +
screenshots as it goes, and records a video of the whole walkthrough for
adversarial review. You get evidence, not a checklist to run yourself.
OUTPUT — bugs bucketed by priority
CRITICAL (blocks ship)
▸ /checkout — "Place order" button does nothing on mobile viewport.
Screenshot attached. This is a revenue-blocker.
▸ /signup — form submits but shows a 500; account not created.
MEDIUM
▸ /dashboard — chart overflows its container below 768px.
▸ /settings — save succeeds but no confirmation; users double-click.
LOW
▸ /about — a stale year in the footer.
▸ /pricing — hover state missing on one CTA.
Each bug: the page, what broke, a screenshot at the moment it broke.
THE VIDEO IS THE POINT
The full walkthrough is recorded so you (or a reviewer) can watch the
app being used adversarially before it ships — you see the critical
checkout bug happen, not just read that it exists. That's what catches
the "works on my machine" class of issue a code review never would.
WHY DOGFOOD-BEFORE-SHIP BEATS "we'll catch it in QA"
The critical bugs above are the ones that only appear when something
actually clicks through the real built app on a real viewport. This runs
that pass automatically, every build, and hands you a ranked list plus
proof.
Point it at your deployed preview URL and it'll produce the ranked
report + video for your actual app.About this skill
Your app loads, but can someone finish signup, save their work, recover from an error, and come back without losing it? This walkthrough exercises real user journeys, deliberately probes fragile transitions, and turns observed failures into reproducible bug reports with screenshots and recording timestamps when available.
What it does
- Maps reachable pages, user roles, and core journeys into a bounded coverage plan.
- Exercises complete tasks, including persistence checks after reload and navigation.
- Probes empty inputs, repeated submissions, cancellation, back navigation, and supported network failure scenarios.
- Captures meaningful screenshots and records the walkthrough when the browser tooling supports it.
- Separates confirmed bugs from suspected problems and ranks findings by actual user impact.
- Reports blocked flows, untested states, duplicate symptoms, and evidence-backed release concerns.
What you get
A prioritized bug report with starting conditions, exact reproduction steps, expected and actual behavior, and linked evidence. You also get a coverage ledger and a walkthrough recording when recording was available and successfully verified.
Best for
Developers and small product teams with a running web app who want an adversarial browser review before a release, demo, or customer handoff.
SKILL.md preview
---
name: pre-ship-app-walkthrough-and-bug-report
description: Conduct an exploratory browser walkthrough of a running app, testing complete user journeys and failure states, then produce reproducible bugs with impact-based severity, screenshots, and recording timestamps when available. Use when the user says "dogfood the app", "walk through this before we ship", "find bugs in my app", "test my app", "record a QA walkthrough", "check the whole app", "it loads but users keep getting stuck", or "my app keeps losing saved changes".
---
# Pre-Ship App Walkthrough and Bug Report
… (sign up to view the full skill)More development skills
View all Development skills →React and Next.js Regression Test Coverage
Generate React and Next.js tests with Jest, Testing Library, MSW, and Playwright, prioritized by regression risk.
Playwright E2E Tests and Flake Repair
Build reliable Playwright tests, repair flakes from evidence, migrate suites, and configure faster, diagnosable CI.
Pre-Ship Verification for Code Changes
Before calling a code change done, Claude grades every claim by evidence, tries to break it, and reports what's verified vs assumed.
TestRail Case and CI Result Sync
Sync automated tests to TestRail cases and scoped runs with stable mappings, retry handling, and verified result counts.