Xcode Compilation Analyzer

avdlee/xcode-build-optimization-agent-skill

When your Swift build takes forever or Xcode spits out type-checking warnings, this skill digs into build timing summaries and frontend diagnostics to find the actual bottlenecks. It runs analysis flags like warn-long-function-bodies, parses CompileSwiftSources tasks, and checks if your incremental builds are getting wrecked by module emission or planning overhead. The output is a ranked list of fixes with expected wall-clock impact, which matters because heavily parallelized builds won't always get faster just by optimizing individual files. It knows the difference between reducing compiler work and actually cutting your wait time, and it won't touch your code without asking first.

skills.sh installs: 3.5K
GitHub stars: 1.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add avdlee/xcode-build-optimization-agent-skill --skill xcode-compilation-analyzer --agent claude-code

Installs into .claude/skills of the current project.

Files

Xcode Compilation Analyzer

Use this skill when compile time, not just general project configuration, looks like the bottleneck.

Core Rules

Start from evidence, ideally a recent .build-benchmark/ artifact or raw timing-summary output.
Prefer analysis-only compiler flags over persistent project edits during investigation.
Rank findings by expected wall-clock impact, not cumulative compile-time impact. When compile tasks are heavily parallelized (sum of compile categories >> wall-clock median), note that fixing individual hotspots may improve parallel efficiency without reducing build wait time.
When the evidence points to parallelized work rather than serial bottlenecks, label recommendations as "Reduces compiler workload (parallel)" rather than "Reduces build time."
Do not edit source or build settings without explicit developer approval.