skills.rest
ChoshimWy
ChoshimWyCOMMUNITY
Explore all skills by this author →
GitHub

debugging

Diagnose iOS runtime issues from logs and symbolicated stacks.

8|Updated Feb 12, 2026
Search Tags:#debugging#ios#instruments#root-cause#lldb#memory-leaks#crash-analysis
One-click install
npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill debugging-choshimwy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/ChoshimWy/iOSAgentSkills/tree/main/skills/debugging
Command: npx skills add https://github.com/ChoshimWy/iOSAgentSkills --skill debugging-choshimwy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

iOS 调试与问题排查技能帮助开发者在遇到 crash、异常、运行时错误、内存泄漏或僵死症状时快速定位根因，提供可执行的分析路径与修复方向。

Core Features & Use Cases

  • 症状识别与分支流程：根据崩溃日志、符号化调用栈和运行时行为判定潜在原因类型。
  • 诊断工具指令与路径：给出 LLDB 命令、Memory Graph 以及 Instruments 的排查路径与操作要点。
  • 场景示例：在应用崩溃或内存泄漏时，提供可复现实例、复现步骤与可执行的修复方向。

Quick Start

Describe the crash or runtime symptom, attach logs and steps to reproduce, and run the debugging workflow to obtain a root-cause analysis with actionable LLDB commands.

Frequently Asked Questions about debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the root cause of an iOS crash from a symbolicated stack trace?▼

To find the root cause of an iOS crash, analyze the symbolicated stack trace alongside reproduction steps to identify the fault type. This diagnostic process isolates the exact runtime failure and provides actionable LLDB commands to inspect the crash state.

What is the best way to diagnose iOS memory leaks and deadlocks?▼

Diagnosing iOS memory leaks and deadlocks requires analyzing runtime behavior and applying Instruments workflows to isolate faulty resource management. This approach guides you through specific Memory Graph inspections to pinpoint the exact retaining object causing the leak.

How do I use LLDB commands to troubleshoot iOS runtime issues and hangs?▼

You can troubleshoot iOS runtime issues and hangs by running targeted LLDB commands to inspect the application's execution state. The debugging workflow analyzes logs and reproduction steps to generate exact LLDB instructions for isolating the hang's root cause.

Can I use this iOS debugging workflow for static analysis and build verification errors?▼

This iOS debugging workflow is designed for runtime issues like crashes, memory leaks, and hangs, not static analysis or build verification. If your issue relates to build or verification failures, you should direct your diagnosis to the verify-ios-build process instead.

Why does my iOS app deadlock and how can I reproduce the issue for root-cause analysis?▼

iOS app deadlocks occur when threads block each other indefinitely, and root-cause analysis requires detailed reproduction steps to trigger the exact runtime state. By analyzing the logs and runtime behavior, the diagnostic workflow isolates the specific threading conflict causing the deadlock.

Related Skills

Explore More Software Engineering Skills→
open-foxopen-fox
54

issue-analyzer

Analyze crash stacks and logs to produce root-cause reports with fix recommendations.

Community
Advanced
yashpalsince2004yashpalsince2004

debugging-instruments

Diagnoses iOS app crashes, memory leaks, and performance bottlenecks using LLDB, Memory Graph, and Instruments.

Community
Advanced
NagyViktNagyVikt
2

ios-debugger-agent

Automate iOS app builds, launches, and log capture on booted simulators.

Community
Advanced
anishi1222anishi1222

memory-leak-check

Detect unclosed resources, static collection growth, and listener leaks in code repositories.

Community
Intermediate