← ClaudeAtlas

apple-bug-flow-reviewlisted

Find real bugs in an Apple app and audit its user journeys end to end — static scan, build-time diagnostics, runtime sanitizers, then a flow-by-flow walk looking for dead ends, lost state and silent failures. Use when the user asks for a bug hunt, a QA pass, a code health check, a crash investigation, or a review before submitting ("בדוק באגים", "תעשה QA"), and after a large change when nothing obvious is broken. It reports with severity and evidence, and fixes only what the user approves. It does NOT review visual design (apple-hig-design-review), App Review policy compliance (app-store-review-compliance), or the web layer of a Capacitor app (capacitor-bug-flow-review).
yybd/app-factory · ★ 5 · Code & Development · score 77
Install: claude install-skill yybd/app-factory
# Apple Bug & User-Flow Review (iOS + macOS) This skill answers one question: **"Is the app actually correct, and does every user journey work?"** — before the user ships it. It hunts for *defects*: logic bugs, fragile code, and places where the user flow breaks (crashes, dead-ends, data loss, broken states). It is the QA pass, not the design pass and not the compliance pass. Be a sharp QA engineer, not a style linter. A finding is only worth reporting if it can actually hurt a user — a crash, wrong result, lost data, a flow the user can't complete, a leak that degrades the app over time. For each finding, give a **concrete repro** (or the exact code path) and a **fix**, and rank by user impact. Call out what's already solid — a credible review isn't all red. **Language**: Write all conversation, findings, and the report in the **`conversational language`** set in the hub `DATA.md` (`$APP_HUB/DATA.md`) — fall back to the language the user writes in if it's unset (e.g. a standalone project with no hub). Write all code, identifiers, test names, and shell commands in **English**. The bug knowledge lives in [references/bug-catalog.md](references/bug-catalog.md) (what to look for, how to detect it, how to fix it). The flow-audit method and state matrix live in [references/flow-audit.md](references/flow-audit.md). How to collect runtime signals (analyzer, sanitizers, SwiftUI runtime warnings, Instruments) lives in [references/runtime-diagnostics.md](references/runtime-diagnosti