Asc Crash Triage
Summarize TestFlight crashes, beta feedback, and performance signals for an iOS build using asc CLI workflows.
Overview
ASC Crash Triage is an agent skill most often used in Ship (also Operate errors, Grow support) that fetches and summarizes TestFlight crashes, beta feedback, and performance diagnostics via asc.
Install
npx skills add https://github.com/rudrankriyam/asc-skills --skill asc-crash-triageWhat is this skill?
- Workflow: resolve app ID, fetch via asc, parse JSON into human-readable summaries
- TestFlight crash list with sort, build, device-model, and OS-version filters
- Beta feedback listing with optional screenshots and build filters
- Table and paginated output modes for larger crash corpora
- Focused on TF crashes, hangs, disk writes, and launch diagnostics language
- Default crash and feedback list limits of 10 newest items in documented commands
Adoption & trust: 912 installs on skills.sh; 845 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have a new TestFlight build and scattered crash and feedback signals with no fast way to see what matters for that app or build.
Who is it for?
Indie iOS developers already using asc who need crash and beta feedback rollups after each TestFlight drop.
Skip if: Android-only apps, greenfield apps with no TestFlight data yet, or teams that do not use asc on the command line.
When should I use this skill?
User asks about TestFlight crashes, TF crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app.
What do I get? / Deliverables
You get a structured crash and feedback summary tied to app and build filters so you can prioritize fixes before the next submission.
- Human-readable crash summary from asc JSON
- Beta feedback digest with optional screenshot context
- Filtered views by build, device, or OS when specified
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Ship because the skill supports pre-release beta quality and crash review on TestFlight builds. Testing subphase matches TF crash reports, beta feedback triage, and hang or launch diagnostics.
Where it fits
After uploading a build, list the ten newest crashes filtered to that build before approving wider beta distribution.
Investigate hang or disk-write diagnostics reported on a specific device model and OS combo.
Summarize recent beta feedback with screenshots to reply to testers with a prioritized fix list.
How it compares
Operational triage workflow around asc CLI, not a hosted crash analytics SaaS or in-Xcode-only symbolication guide.
Common Questions / FAQ
Who is asc-crash-triage for?
Solo and small-team iOS builders monitoring TestFlight who want agent-driven summaries from asc instead of manual Connect clicking.
When should I use asc-crash-triage?
In Ship during beta testing when reviewing a build’s crashes; in Operate when diagnosing recurring hangs or launch issues; in Grow support when responding to tester feedback clusters.
Is asc-crash-triage safe to install?
It instructs the agent to run asc against your Apple developer context; review the Security Audits panel on this page and limit API keys and shell access to trusted environments.
SKILL.md
READMESKILL.md - Asc Crash Triage
# asc crash triage Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics. ## Workflow 1. Resolve the app ID if not provided (use `asc apps list`). 2. Fetch data with the appropriate command. 3. Parse JSON output and present a human-readable summary. ## TestFlight crash reports List recent crashes (newest first): - `asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10` - Filter by build: `asc testflight crashes list --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10` - Filter by device/OS: `asc testflight crashes list --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0"` - All crashes: `asc testflight crashes list --app "APP_ID" --paginate` - Table view: `asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10 --output table` ## TestFlight beta feedback List recent feedback (newest first): - `asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10` - With screenshots: `asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10 --include-screenshots` - Filter by build: `asc testflight feedback list --app "APP_ID" --build "BUILD_ID" --sort -createdDate` - All feedback: `asc testflight feedback list --app "APP_ID" --paginate` ## Performance diagnostics (hangs, disk writes, launches) Requires a build ID. Resolve via `asc builds info --app "APP_ID" --latest --platform IOS` or `asc builds list --app "APP_ID" --sort -uploadedDate --limit 5`. - List diagnostic signatures: `asc performance diagnostics list --build "BUILD_ID"` - Filter by type: `asc performance diagnostics list --build "BUILD_ID" --diagnostic-type "HANGS"` - Types: `HANGS`, `DISK_WRITES`, `LAUNCHES` - View logs for a signature: `asc performance diagnostics view --id "SIGNATURE_ID"` - Download all metrics: `asc performance download --build "BUILD_ID" --output ./metrics.json` ## Resolving IDs - App ID from name: `asc apps list --name "AppName"` or `asc apps list --bundle-id "com.example.app"` - Latest build ID: `asc builds info --app "APP_ID" --latest --platform IOS` - Recent builds: `asc builds list --app "APP_ID" --sort -uploadedDate --limit 5` - Set default: `export ASC_APP_ID="APP_ID"` ## Summary format When presenting results, organize by severity and frequency: 1. **Total count** — how many crashes/feedbacks in the result set. 2. **Top crash signatures** — group by exception type or crash reason, ranked by count. 3. **Affected builds** — which build versions are impacted. 4. **Device & OS breakdown** — most affected device models and OS versions. 5. **Timeline** — when crashes started or spiked. For performance diagnostics, highlight the highest-weight signatures first. ## Notes - Default output is JSON; use `--output table` or `--output markdown` for quick human review. - Use `--paginate` to fetch all pages when doing a full analysis. - Use `--pretty` with JSON for debugging command output. - Crash data from App Store Connect may have 24-48h delay.