apple-bug-flow-review SKILL.md skillA
apple-bug-flow-review from yybd/app-factory is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yybd/app-factory/apple-bug-flow-review@git:20260929.a7fd8b7Pins git:20260929.a7fd8b7 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yybd/app-factory
- Path
plugins/apple-track/skills/apple-bug-flow-review/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260929.a7fd8b7, committed Sep 29, 2026
- Size
- 13,900 bytes
- Repository stars
- 5
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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) …
Read the whole file at its exact version.
How to install
mdr add yybd/app-factory/apple-bug-flow-review@sha256:eab2d17328fa4576The line at the top of this page pins the label git:20260929.a7fd8b7, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_a4icqjzweh65s7ss)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 29, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (13900 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yybd/app-factory · 5 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_a4icqjzweh65s7ss GET https://markdownregistry.com/api/v1/resolve?ref=yybd/app-factory/apple-bug-flow-review GET https://markdownregistry.com/api/v1/blob/eab2d17328fa4576027430682fc47a2efd7a0d2724c69a0bd733fb08ad7dc641
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.