xcode-compilation-analyzer

Analyze Swift compile hotspots from timing summaries and diagnostics to produce a prioritized optimization plan.

103|6|Updated Aug 2, 2025
One-click install
npx skills add https://github.com/n0an/VivaDicta --skill xcode-compilation-analyzer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xcode-compilation-analyzer
Source: https://github.com/n0an/VivaDicta/tree/main/.agents/skills/xcode-compilation-analyzer
Command: npx skills add https://github.com/n0an/VivaDicta --skill xcode-compilation-analyzer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan to speed up compilation.

Core Features & Use Cases

  • Identify bottlenecks in Swift and mixed-language compilation by correlating Build Timing Summary data with diagnostics.
  • Generate a prioritized, source-level optimization plan that targets the biggest wall-clock improvements.
  • Suitable for scenarios such as slow CompileSwiftSources, large SwiftEmitModule times, or heavy incremental-build replanning, delivering actionable recommendations.

Quick Start

Run the diagnostic workflow on a project with slow builds to generate a prioritized optimization plan.

Frequently Asked Questions about xcode-compilation-analyzer

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

FAQPage Schema
How do I identify Swift compilation hotspots from Xcode build timing summaries?

Analyze slow CompileSwiftSources by correlating Build Timing Summary data with Swift frontend diagnostics to locate exact source-level bottlenecks. This produces a prioritized optimization plan targeting the biggest wall-clock improvements.

Why does my incremental build take so long due to heavy module planning?

Heavy incremental-build replanning often stems from complex module dependencies triggering extensive SwiftEmitModule times. Analyzing frontend diagnostics exposes these structural hotspots, enabling targeted source-level adjustments to reduce replanning overhead.

What is the best way to speed up slow Xcode builds without modifying project configuration?

Speed up Xcode builds through analysis-only adjustments by generating a prioritized, source-level optimization plan from recent timing artifacts. This recommend-first approach targets wall-clock improvements without requiring persistent edits.

Does this compilation analysis approach work for mixed-language Swift projects?

Yes, this compilation analysis works for mixed-language projects by correlating Build Timing Summary data across both Swift and Objective-C frontend diagnostics. It identifies cross-language compilation bottlenecks to deliver actionable recommendations.

Do I need existing build benchmark artifacts to start diagnosing compilation bottlenecks?

You need recent evidence artifacts like .build-benchmark logs or timing summaries to start diagnosing compilation bottlenecks. The analysis uses these existing artifacts to generate a ranked list of actionable source-level recommendations.