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
Install / Use
npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-compilation-analyzerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of xcode-compilation-analyzer
xcode-compilation-analyzer scores 82/100 on our quality scale, 3376th of 4,698 Development & Engineering skills we index.
Its SKILL.md is 5.3 KB long, well organised into 8 sections and no code examples: a solid amount of guidance for an agent.
With 1,235 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so xcode-compilation-analyzer is actively maintained.
- Our last check on 2026-11-07 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
xcode-compilation-analyzer compared with similar skills
All 4 of these similar skills score higher than xcode-compilation-analyzer; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| xcode-compilation-analyzer (this skill)by AvdLee | 82 | 1.2k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install xcode-compilation-analyzer?
- Run
npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-compilation-analyzer. The install tabs above show the steps for each supported agent. - Which AI agents does xcode-compilation-analyzer work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is xcode-compilation-analyzer safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is xcode-compilation-analyzer still maintained?
- The repository was last updated about 2 months ago, so xcode-compilation-analyzer is actively maintained.
Skill content
View source on GitHubname: xcode-compilation-analyzer description: 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.
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 Summaryoutput from clean and incremental builds- long-running
CompileSwiftSourcesor per-file compilation tasks SwiftEmitModuletime -- can reach 60s+ after a single-line change in large modules; if it dominates incremental builds, the module is likely too large or macro-heavyPlanning Swift moduletime -- if this category is disproportionately large in incremental builds (up to 30s per module), it signals unexpected input invalidation or macro-related rebuild cascading- ad hoc runs with:
-Xfrontend -warn-long-expression-type-checking=<ms>-Xfrontend -warn-long-function-bodies=<ms>
- deeper diagnostic flags for thorough investigation:
-Xfrontend -debug-time-compilation-- per-file compile times to rank the slowest files-Xfrontend -debug-time-function-bodies-- per-function compile times (unfiltered, complements the threshold-based warning flags)-Xswiftc -driver-time-compilation-- driver-level timing to isolate driver overhead-Xfrontend -stats-output-dir <path>-- detailed compiler statistics (JSON) per compilation unit for root-cause analysis
- mixed Swift and Objective-C surfaces that increase bridging work
Analysis Workflow
- Identify whether the main issue is broad compilation volume or a few extreme hotspots.
- Parse timing-summary categories and rank the biggest compile contributors.
- Run the diagnostics script to surface type-checking hotspots:
This produces a ranked list of functions and expressions that exceed the millisecond threshold. Use the diagnostics artifact alongside source inspection to focus on the most expensive files first.python3 scripts/diagnose_compilation.py \ --project App.xcodeproj \ --scheme MyApp \ --configuration Debug \ --destination "platform=iOS Simulator,name=iPhone 16" \ --threshold 100 \ --output-dir .build-benchmark - Map the evidence to a concrete recommendation list.
- Separate code-level suggestions from project-level or module-level suggestions.
Apple-Derived Checks
Look for these patterns first:
- missing explicit type information in expensive expressions
- complex chained or nested expressions that are hard to type-check
- delegate properties typed as
AnyObjectinstead of a concrete protocol - oversized Objective-C bridging headers or generated Swift-to-Objective-C surfaces
- header imports that skip framework qualification and miss module-cache reuse
- classes missing
finalthat are never subclassed - overly broad access control (
public/open) on internal-only symbols - monolithic SwiftUI
bodyproperties that should be decomposed into subviews - long method chains or closures without intermediate type annotations
Reporting Format
For each recommendation, include:
- observed evidence
- likely affected file or module
- expected wait-time impact (e.g. "Expected to reduce your clean build by ~2s" or "Reduces parallel compile work but unlikely to reduce build wait time")
- confidence
- whether approval is required before applying it
If the evidence points to project configuration instead of source, hand off to xcode-project-analyzer by reading its SKILL.md and applying its workflow to the same project context.
Preferred Tactics
- Suggest ad hoc flag injection through the build command before recommending persistent build-setting changes.
- Prefer narrowing giant view builders, closures, or result-builder expressions into smaller typed units.
- Recommend explicit imports and protocol typing when they reduce compiler search space.
- Call out when mixed-language boundaries are the real issue rather than Swift syntax alone.
Additional Resources
- For the detailed audit checklist, see references/code-compilation-checks.md
- For the shared recommendation structure, see references/recommendation-format.md
- For source citations, see references/build-optimization-sources.md
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
