debugging▌

Diagnose crashes, memory leaks, retain cycles, main thread hangs, and performance bottlenecks in iOS apps using LLDB, Memory Graph Debugger, and Instruments. Covers breakpoint workflows, memory graph analysis, hang detection, build failure triage, and Instruments profiling for CPU, memory, energy, and network.

Structured debugging methodology that enforces root cause investigation before attempting any fix. \n \n Enforces four sequential phases: root cause investigation, pattern analysis, hypothesis testing, and implementation; skipping phases or proposing fixes prematurely triggers a redirect \n Includes diagnostic instrumentation patterns for multi-component systems, data flow tracing techniques, and explicit red flags that signal you're guessing rather than investigating \n Stops after three failed

You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.

Systematic debugging methodology with tools, techniques, and patterns for tracking down bugs across any codebase. \n \n Covers the scientific method for debugging: observe, hypothesize, experiment, analyze, and repeat until root cause is found \n Includes language-specific debugging tools and configurations for JavaScript/TypeScript, Python, and Go with practical examples \n Provides advanced techniques like binary search debugging, differential debugging, trace debugging, and memory leak detect

Intermittent issues are the most difficult to debug because they don't occur consistently. Systematic approach and comprehensive monitoring are essential.

Use this skill when:

Use when:

Check dependencies BEFORE blaming code. Core principle 80% of persistent build failures are dependency resolution issues (CocoaPods, SPM, framework conflicts), not code bugs.

Browser debugging tools help identify and fix client-side issues including JavaScript errors, layout problems, and performance issues.

$22