Xcode Build Benchmark

avdlee/xcode-build-optimization-agent-skill

This does one thing well: it runs repeatable Xcode build benchmarks so you have numbers before you start optimizing. It measures clean builds, cached clean builds (when compilation cache is on), zero-change builds to find fixed overhead, and optional incremental builds with a file touch. Everything gets run three times and saved to timestamped JSON in `.build-benchmark/` so you can compare before and after. The workflow is opinionated about consistency, it won't modify your project files, and it explicitly stops after measuring unless you ask for optimization help. If your build times feel slow but you don't have a baseline, start here.

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-build-benchmark --agent claude-code

Installs into .claude/skills of the current project.

Files

Xcode Build Benchmark

Use this skill to produce a repeatable Xcode build baseline before anyone tries to optimize build times.

Core Rules

Measure before recommending changes.
Capture clean and incremental builds separately.
Keep the command, destination, configuration, scheme, and warm-up rules consistent across runs.
Write a timestamped JSON artifact to .build-benchmark/.
Do not change project files as part of benchmarking.

Inputs To Collect

Confirm or infer:

workspace or project path
scheme
configuration
destination
whether the user wants simulator or device numbers
whether a custom DerivedData path is needed

If the project has both clean-build and incremental-build pain, benchmark both. That is the default.

Worktree Considerations

When benchmarking inside a git worktree, SPM packages with exclude: paths that reference gitignored directories (e.g., __Snapshots__) will cause xcodebuild -resolvePackageDependencies to crash. Create those missing directories before running any builds.