agentleFS
Sign inStart free
VelimirMuellerVelimirMueller/ai-development-skills/skills/swift/asc-crash-triage/SKILL.md

asc-crash-triage

Skill7 starsChanged 18 days agoMITView on GitHub

Use when the user asks about TF crashes, TestFlight crash reports, beta tester feedback, app hangs, disk writes, launch diagnostics, or wants a crash summary for a build or app. Triage TestFlight crashes, beta feedback, and performance diagnostics using asc.

8 other projects use a version of this, 7 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. 2 are common, 1 is distinctive, and 2 are very specific to this project.

  • 2

    Common

    Most of the 7 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.

    line 8
  2. Common:

    When presenting results, organize by severity and frequency:

    line 54
  3. Distinctive:

    Read-command output defaults to table in a terminal and JSON in pipes or CI.

    line 66
  4. Very specific:

    Use --paginate to fetch all pages when doing a full analysis.

    line 67
  5. Very specific:

    Use --pretty with JSON for debugging command output.

    line 68

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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, using --output json for responses that will be parsed. For performance download, --output is the destination file path.
  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-id "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-id "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-id "BUILD_ID"
  • Filter by type: asc performance diagnostics list --build-id "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-id "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

  • Read-command output defaults to table in a terminal and JSON in pipes or CI. Select the format explicitly when parsing results.
  • 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free