New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Xcode Compilation Analyzer

by omarshahine in omarshahine/HomeClaw

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

MITAuto-check passedMobile

Install Xcode Compilation Analyzer

skills CLI
$ npx skills add omarshahine/HomeClaw --skill xcode-compilation-analyzer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install omarshahine/HomeClaw xcode-compilation-analyzer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/omarshahine/HomeClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/xcode-compilation-analyzer .claude/skills/xcode-compilation-analyzer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
xcode-compilation-analyzer
GitHub stars
176
Used in
1 other repo
Token cost
~1.4k tokens
SKILL.md length
564 words
Files
5 (incl. scripts, references)
Skills in repo
14
Repo updated
First seen
Licence
MIT

At a glance

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

  • Works in 5 steps: Identify whether the main issue is broad… → Parse timing-summary categories and rank… → Run the diagnostics script to surface… → …
  • A developer reports slow compilation
  • SKILL.md covers Core Rules, What To Inspect, Analysis Workflow and Apple-Derived Checks, plus 3 more sections
  • Runs Python scripts from its folder; calls python3

What it does

Xcode Compilation Analyzer is an agent skill from omarshahine/HomeClaw. 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.

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/build-optimization-sources.md`, `references/code-compilation-checks.md` and `references/recommendation-format.md`).

It sits in Mobile, covering iOS development and Type safety. It works with Xcode. The repository describes itself as: HomeKit smart home control via MCP — lights, locks, thermostats, and scenes for Claude Desktop, Claude Code, and OpenClaw. The licence is MIT.

When your agent uses it

  • A developer reports slow compilation
  • Type-checking warnings
  • Expensive clean-build compile phases
  • Long CompileSwiftSources tasks

Example prompts

  • “/xcode-compilation-analyzer”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Identify whether the main issue is broad compilation volume or a few extreme hotspots.
  2. Parse timing-summary categories and rank the biggest compile contributors.
  3. Run the diagnostics script to surface type-checking hotspots
  4. Map the evidence to a concrete recommendation list.
  5. Separate code-level suggestions from project-level or module-level suggestions.

What it can do on your machine

Read from SKILL.md and the folder at commit da69700. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Xcode Compilation Analyzer loads about 1.4k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 104 tokens; SKILL.md has 564 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~104
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from omarshahine/HomeClaw at commit da69700, republished under its MIT licence (© omarshahine). 564 words, ~1,362 tokens.

Download SKILL.mdSave it as .claude/skills/xcode-compilation-analyzer/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
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 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
  • Planning Swift module time -- 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

  1. Identify whether the main issue is broad compilation volume or a few extreme hotspots.
  2. Parse timing-summary categories and rank the biggest compile contributors.
  3. Run the diagnostics script to surface type-checking hotspots:
    bash
    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
    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.
  4. Map the evidence to a concrete recommendation list.
  5. Separate code-level suggestions from project-level or module-level suggestions.
Show full SKILL.md (234 more words)Show less

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 AnyObject instead 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 final that are never subclassed
  • overly broad access control (public/open) on internal-only symbols
  • monolithic SwiftUI body properties 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

© omarshahine, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references) in .claude/skills/xcode-compilation-analyzer of omarshahine/HomeClaw.

  • SKILL.md
  • references/build-optimization-sources.md
  • references/code-compilation-checks.md
  • references/recommendation-format.md
  • scripts/diagnose_compilation.py

Open the folder on GitHubat commit da69700

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in omarshahine/HomeClaw, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Xcode Compilation Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Xcode Compilation Analyzer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Xcode Compilation Analyzer this skillomarshahine/HomeClaw1761 repos~1.4kAutomated safety check: PassMIT
macOS Spm App PackagingDimillian/Skills4k5 repos~1.2kAutomated safety check: PassMIT
Orca iOS Simulator Controlstablyai/orca87k1 repos~584Automated safety check: PassApache-2.0
Apple Crash Log .NET Symbolicationdotnet/skills5.6k1 repos~2.4kAutomated safety check: PassMIT
Update Swiftui APIsAvdLee/SwiftUI-Agent-Skill3.7k—~1.2kAutomated safety check: PassMIT
iOS Simulator Skillconorluddy/ios-simulator-skill1.3k—~5.7kAutomated safety check: PassMIT

Similar skills

  • macOS Spm App Packaging

    Dimillian/Skills

    Scaffold, build, and package SwiftPM-based macOS apps without an Xcode project.

    4k GitHub starsUsed in 5 repos~1.2k tokens
    MobileAuto-check passed

  • Orca iOS Simulator Control

    stablyai/orca

    iOS Simulator control from inside Orca, with the live device view in Orca's emulator pane. Use when driving a booted Apple Simulator on macOS: taps, gestures…

    87k GitHub starsUsed in 1 repo~584 tokens
    MobileAuto-check passed

  • Apple Crash Log .NET Symbolication

    dotnet/skills

    Official

    Resolves .NET runtime frames in Apple .ips crash logs to function names, source files and line numbers using dSYM symbols, atos and the Microsoft symbol server.

    5.6k GitHub starsUsed in 1 repo~2.4k tokens
    MobileAuto-check passed

  • Update Swiftui APIs

    AvdLee/SwiftUI-Agent-Skill

    Scan Apple's SwiftUI documentation for deprecated APIs and update the SwiftUI Expert Skill with modern replacements.

    3.7k GitHub stars~1.2k tokensUpdated 2 days ago
    MobileAuto-check passed

  • iOS Simulator Skill

    conorluddy/ios-simulator-skill

    29 production-ready scripts for iOS app testing, building, and automation.

    1.3k GitHub stars~5.7k tokensUpdated 2 days ago
    MobileAuto-check passed

  • Macios Xcode Beta Update

    dotnet/macios

    Official

    Update dotnet/macios to a new Xcode beta and validate it end-to-end.

    2.9k GitHub stars~1.8k tokensUpdated today
    MobileAuto-check passed

More from omarshahine/HomeClaw

All 14 skills in this repo

  • Swiftui Expert Skill

    omarshahine/HomeClaw

    A skill your agent uses when writing, reviewing, or refactoring SwiftUI code for iOS or macOS, including state management, view composition, performance, Liquid Glass adoption, or Instruments .trace…

    176 GitHub starsUsed in 4 repos~2.8k tokens
    Auto-check passed

  • Spm Build Analysis

    omarshahine/HomeClaw

    Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds.

    176 GitHub starsUsed in 1 repo~1.5k tokens
    Auto-check passed

  • Xcode Build Benchmark

    omarshahine/HomeClaw

    Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped .build-benchmark/ artifacts.

    176 GitHub starsUsed in 1 repo~1.2k tokens
    Auto-check passed

  • Xcode Build Fixer

    omarshahine/HomeClaw

    Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement.

    176 GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed

  • Xcode Build Orchestrator

    omarshahine/HomeClaw

    Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to…

    176 GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed

  • iOS Ettrace Performance

    omarshahine/HomeClaw

    Capture and interpret ETTrace profiles for iOS simulator apps, including symbolicated launch and runtime flamegraphs.

    176 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Works with

Categories

Questions about Xcode Compilation Analyzer

What does Xcode Compilation Analyzer 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. Xcode Compilation Analyzer is an agent skill from omarshahine/HomeClaw. Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan.

When should I use Xcode Compilation Analyzer?

Xcode Compilation Analyzer fits situations like: A developer reports slow compilation; type-checking warnings; expensive clean-build compile phases; long CompileSwiftSources tasks.

How do I install Xcode Compilation Analyzer in Claude Code?

Run `npx skills add omarshahine/HomeClaw --skill xcode-compilation-analyzer -a claude-code`. Or copy the skill folder (.claude/skills/xcode-compilation-analyzer in omarshahine/HomeClaw) into .claude/skills/xcode-compilation-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Xcode Compilation Analyzer in Codex?

Run `npx skills add omarshahine/HomeClaw --skill xcode-compilation-analyzer -a codex`. Or copy the skill folder (.claude/skills/xcode-compilation-analyzer in omarshahine/HomeClaw) into .agents/skills/xcode-compilation-analyzer in your project. Codex loads it when a task matches its description.

Can I use Xcode Compilation Analyzer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add omarshahine/HomeClaw --skill xcode-compilation-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/xcode-compilation-analyzer, .gemini/skills/xcode-compilation-analyzer, .github/skills/xcode-compilation-analyzer and .opencode/skills/xcode-compilation-analyzer in your project.

What does Xcode Compilation Analyzer need to run?

Going by SKILL.md and its folder, Xcode Compilation Analyzer needs Python for the scripts in its folder and the command-line tools its instructions call (python3). Our summary lists: Python 3.

Does Xcode Compilation Analyzer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Xcode Compilation Analyzer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Xcode Compilation Analyzer use?

Xcode Compilation Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Xcode Compilation Analyzer use?

About 1.4k tokens (SKILL.md is roughly 5.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 4.2k tokens, read only when the agent opens those files.

What are the alternatives to Xcode Compilation Analyzer?

Skills that share tags, products or a category with Xcode Compilation Analyzer: macOS Spm App Packaging (Dimillian/Skills, 4k stars), Orca iOS Simulator Control (stablyai/orca, 87k stars), Apple Crash Log .NET Symbolication (dotnet/skills, 5.6k stars) and Update Swiftui APIs (AvdLee/SwiftUI-Agent-Skill, 3.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Xcode Compilation Analyzer?

omarshahine (a GitHub user) maintains it in omarshahine/HomeClaw, which has 176 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 8, 2026.

Source: omarshahine/HomeClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.