argent-native-profiler

Profile iOS apps with xctrace and analyze exported traces for CPU, hang, and leak bottlenecks.

1.9k|65|Updated Feb 23, 2026

Search Tags:#debugging #memory leaks #trace analysis #xctrace #cpu hotspots #native profiling #ui hangs

Ready to run

npx skills add https://github.com/software-mansion/argent --skill argent-native-profiler-software-mansion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: argent-native-profiler
Source: https://github.com/software-mansion/argent/tree/main/packages/skills/skills/argent-native-profiler
Command: npx skills add https://github.com/software-mansion/argent --skill argent-native-profiler-software-mansion

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Native performance issues like CPU hotspots, UI hangs, and memory leaks are hard to reproduce and explain with logs alone, so teams waste time guessing instead of measuring.

Core Features & Use Cases

Native profiling capture (iOS): Start and stop an Xcode Instruments (xctrace) recording to collect trace data for CPU, hangs, and leaks.
Structured bottleneck analysis: Analyze exported trace files into categorized findings sorted by severity (RED/YELLOW).
Interactive drill-down: Query specific bottleneck details (hang stacks, function callers, thread breakdown, and leak stack evidence) and iterate on investigation.

Quick Start

Use native profiling to capture a before-state trace for an iOS device or simulator run and ask for an analysis of CPU hotspots, UI hangs, and memory leaks from the recorded session.

Frequently Asked Questions about argent-native-profiler

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

FAQPage Schema

How do I diagnose native CPU hotspots and UI hangs in an iOS app?▼

Diagnose native CPU hotspots and UI hangs by profiling an iOS app using an xctrace-backed pipeline to record trace data, then parsing the exported XML into categorized severity findings.

What is the best way to find the root cause of a memory leak using xctrace?▼

Find memory leak root causes by running an xctrace recording, stopping it, and analyzing the exported trace XML to extract interactive drill-down queries like leak stack evidence.

Do I need a specific device UDID to profile an iOS app for performance issues?▼

Yes, profiling an iOS app requires device targeting via a UDID. You also need xctrace availability via Xcode command-line tools installed on your PATH.

Can I drill down into specific thread breakdowns and hang stacks from a trace export?▼

Yes, you can drill down into specific hang stacks, function callers, thread breakdowns, and leak stack evidence by running interactive queries on the parsed trace export.

Does this native profiling workflow support platforms other than iOS?▼

No, this native profiling workflow is iOS-only. It applies an xctrace-backed pipeline to capture trace data for CPU, hangs, and leaks specifically on iOS devices or simulators.

Why are my native performance bottleneck findings categorized as RED or YELLOW?▼

Bottleneck findings are categorized as RED or YELLOW to sort trace analysis results by severity, helping prioritize which CPU hotspots, UI hangs, or memory leaks to investigate first.