crash-debugging
Skill1 starsChanged 2 months agoMITView on GitHub
Diagnose macOS and iOS crash reports by establishing build identity, symbolication quality, faulting path, and confidence before naming a root cause.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- conorluddy/xclaude-plugintheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- conorluddy/xclaude-plugin★ 186same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository39 other files it gives its agents.
- apple-native-motionSkill
- apple-ui-copySkill
- audit-macos-appSkill
- brain-wikiSkill
- catch-me-upSkill
- checkpointSkill
- claude-md-coachSkill
- claudeSkill
- codexSkill
- cut-memorySkill
- explaining-problemsSkill
- file-batch-safetySkill
- handoffSkill
- heads-downSkill
- hopper-mcpSkill
- icon-designSkill
- interface-integritySkill
- ios-defaultsSkill
- kitSkill
- macos-defaultsSkill
- mock-and-pickSkill
- obsess-heroSkill
- obsessSkill
- offline-archiveSkill
- os-workaroundsSkill
- paper-mcpSkill
- predictionSkill
- second-loopSkill
- session-auditSkill
- ship-macosSkill
- show-meSkill
- slice-and-reviewSkill
- slow-modeSkill
- spatial-interfacesSkill
- standupSkill
- synthetic-fixturesSkill
- transitional-interfacesSkill
- web-design-defaultsSkill
- window-captureSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- Very specific: line 13
Read Application Specific Information, exception notes, termination reason, and any Last Exception Backtrace before interpreting ordinary …
- Distinctive: line 25
Read the crashed thread bottom-up to the first relevant project frame.
- Very specific: line 35
If the minimal reproduction proves an Apple or framework defect, route the compatibility code through os-workarounds.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Crash debugging
Diagnose first. Do not change code unless the user also asked for a fix.
Establish evidence quality
- Identify app version, build number, OS, architecture, timestamp, incident ID, and whether the report belongs to the build under discussion.
- Read
Application Specific Information, exception notes, termination reason, and any Last Exception Backtrace before interpreting ordinary frames. - Grade symbolication: complete, partial, or absent. Confirm that the binary and dSYM UUIDs match before trusting resolved names.
- State what evidence is missing and what it prevents you from distinguishing.
Follow the fault
EXC_BREAKPOINTin Swift often indicates a runtime trap; use the runtime message to distinguish nil unwrap, bounds, and explicit precondition failures.EXC_BAD_ACCESS/SIGSEGVmeans invalid memory access; a near-zero address suggests nil, while other addresses may indicate lifetime or race failures.SIGABRTwith an Objective-C exception is usually named in the exception reason and Last Exception Backtrace.0x8badf00dis a watchdog termination; find synchronous work blocking the watched process or extension.- jetsam and
EXC_RESOURCEare resource terminations; use memory, CPU, or I/O evidence rather than guessing from one frame.
Read the crashed thread bottom-up to the first relevant project frame. Check whether UI was touched off the main thread. Inspect recent history only after establishing the faulting files; recency is a lead, not proof.
Symbolicate when needed
For local builds, find the matching dSYM beside the built product or in the archive. Compare UUIDs with dwarfdump --uuid. Use the current Xcode toolchain's documented symbolication route; if using atos, verify its local syntax and the image load address first.
Report
Lead with one of: confirmed root cause, best-supported diagnosis, or insufficient evidence. Then name the trigger, mechanism, faulting component, supporting lines/frames, smallest plausible fix, and one verification. Separate alternative hypotheses and state the observation that would settle them.
If the minimal reproduction proves an Apple or framework defect, route the compatibility code through os-workarounds.
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
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.