xcode-compilation-analyzer
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-compilation-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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. ## What To Inspect - `Build Timing Summary` output from clean and incremental builds - long-running `CompileSwiftSources` or per-file compilation tasks - `SwiftEmitModule` time -- can reach 60s+ after a single-line change in large modules; if it dominates incremental builds, the module is likely too large or macro-heavy - `Plan
- Core Rules
- What To Inspect
- Analysis Workflow
- Apple-Derived Checks
- Reporting Format
- Preferred Tactics
- Additional Resources
python3 scripts/diagnose_compilation.py \
What does the xcode-compilation-analyzer skill do?
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
How do I install it?
Run `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-compilation-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From AvdLee/Xcode-Build-Optimization-Agent-Skill, a repository with 1,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.