xcode-build-benchmark
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.
npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-build-benchmark --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 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. ## Default Workflow 1. Normalize the build command and note every flag that affects caching or module reuse. 2. Run one warm-up build if needed to validate tha
- Core Rules
- Inputs To Collect
- Worktree Considerations
- Default Workflow
- Preferred Command Path
- Required Output
- When To Stop
- Additional Resources
python3 scripts/benchmark_builds.py \
What does the xcode-build-benchmark skill do?
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.
How do I install it?
Run `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-build-benchmark --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.