SkillVaultskills Browse all 500 skills

Debugging · Version 1.6.0 · Reviewed 2026-08-02

iOS Crash Investigator

Diagnose crash-log symbolication and watchdog diagnosis with evidence, explicit trade-offs, and a verification plan.

4 method steps 4 documented failure modes 4 diagnostic checks 7 quality gates

Interprets iOS crash logs, symbolication, watchdog terminations, memory pressure, concurrency faults, and lifecycle-specific failures.

₹99 one-time

Get this skill archive

What this skill helps you do

  • Crash-log symbolication
  • Watchdog diagnosis
  • Memory termination analysis

How iOS Crash Investigator works

You provide

Symptoms, timestamps, recent changes, and logs

It inspects

Correlated subset and first failing component for crash-log symbolication

It decides

A ranked cause for watchdog diagnosis that explains recovery too

You verify

The cheapest discriminating test, run before the fix

What it checks first

iOS Crash Investigator interprets iOS crash logs, symbolication, watchdog terminations, memory pressure, concurrency faults, and lifecycle-specific failures. Use it when the work involves Crash-log symbolication, Watchdog diagnosis, Memory termination analysis.

  1. The precise first failure time and whether it is a step change or gradual degradation.
  2. What changed within the preceding window: deploy, config, flag, traffic shape, or data.
  3. Whether the failure is universal or correlated with a subset (region, tenant, version, device).
  4. Whether the error is deterministic on retry, which separates a logic defect from a timing or capacity defect.

Failure modes it recognizes

  • A symptom appearing in a component that merely shares a resource with the failing one.
  • An error message describing the last effect rather than the original cause.
  • A latent bug activated by a data value that first appeared in production traffic.
  • A retry layer masking an underlying failure until it saturates and fails loudly.

Answers it will reject

  • Accepting the first plausible hypothesis without testing an alternative that would falsify it.
  • Changing several variables at once, making the recovery unattributable.
  • Trusting a log timestamp without confirming clock alignment across hosts.

Decision rules it applies

  • A valid explanation must account for onset, all symptoms, the affected subset, and the recovery.
  • Choose the test that eliminates the most hypotheses per unit of effort.
  • If nothing in the system changed, examine the inputs.

Evidence it asks for

  • Reconstruct a timestamped timeline from artifacts, not memory.
  • Break metrics down by dimension to isolate the correlated subset.
  • Reproduce in a controlled environment before attempting a fix.

The method inside

  1. Establish what is actually true about crash-log symbolication from the supplied evidence, and mark what is missing.
  2. Identify the mechanism behind watchdog diagnosis rather than restating the symptom.
  3. Choose the smallest defensible change for memory termination analysis, weighing impact, confidence, effort, and reversibility.
  4. Update confidence only when evidence changes

Deliverables

  • Crash-log symbolication assessment
  • Watchdog diagnosis decision and action plan
  • Memory termination analysis verification checklist

Evidence requirements

  • Exact symptoms and timestamps
  • Reproduction conditions and recent changes
  • Logs, traces, metrics, code, or configuration

Quality gates

  • Every material claim traces to supplied evidence or is labeled as a hypothesis.
  • The response follows the declared deliverable contract.
  • No execution, access, measurement, or verification is invented.
  • Secrets and personal data are redacted rather than repeated.
  • The user receives a concrete independent verification step.
  • The relevant failure modes in this domain were considered rather than only the reported symptom.
  • No listed anti-pattern was recommended as a solution.

Example task

Input

Users report the app suddenly closing during background upload, but our crash reporter records no exception.

Expected output

This is likely an OS termination rather than a thrown crash. Inspect MetricKit and device logs for watchdog or jetsam events; background execution limits and memory pressure explain why exception capture is absent...

Boundaries and compatibility

Ideal for

  • Crash-log symbolication: produce a decision or artifact grounded in supplied evidence.
  • Watchdog diagnosis: produce a decision or artifact grounded in supplied evidence.
  • Memory termination analysis: produce a decision or artifact grounded in supplied evidence.

Out of scope

  • Guessing a root cause from a symptom alone
  • Claiming a fix worked without test evidence

Agent compatibility

  • GitHub Copilot custom agents
  • Claude Agent Skills / SKILL.md
  • Any instruction-following chat model

Tool policy: Advisory by default. No tools are assumed. If the host provides tools, use read-only evidence gathering unless the user explicitly approves a scoped write or execution action.