Agent skill · Workflow & Productivity

xcode-build-fixer

Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level compilation fixes, or SPM restructuring that was recommended by an analysis skill.

AvdLeegithub.com/AvdLeeGitHub ↗
claude-codeships scriptsMIT
Install
npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-build-fixer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 12 KB
Bundled scripts: yes
Path: skills/xcode-build-fixer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,193
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Xcode Build Fixer Use this skill to implement approved build optimization changes and verify them with a benchmark. ## Core Rules - Only apply changes that have explicit developer approval. - Apply one logical fix at a time so changes are reviewable and reversible. - Re-benchmark after applying changes to verify improvement. - Report exactly what changed, which files were touched, and the measured delta. - If a change produces no improvement or causes a regression, flag it immediately. ## Inputs The fixer expects one of: - An approved optimization plan at `.build-benchmark/optimization-plan.md` with checked approval boxes. - An explicit developer instruction describing the fix to apply (e.g., "set `DEBUG_INFORMATION_FORMAT` to `dwarf` for Debug"). When working from an optimization plan, read the approval checklist and implement only the checked items. ## Fix Categories ### Build Settings Change `project.pbxproj` values to match the recommendations in [build-settings-best-practices.md](references/build-settings-best-practices.md). Typical fixes: - Set `DEBUG_INFORMATION_FORMAT = dwarf` for Debug - Set `SWIFT_COMPILATION_MODE = singlefile` for Debug - Enable `COMPILATION_CACHE_ENAB

What's inside
Steps it walks through
  1. Core Rules
  2. Inputs
  3. Fix Categories
  4. Build Settings
  5. Script Phases
  6. Source-Level Compilation Fixes
  7. SPM Restructuring
  8. Execution Workflow
  9. Evaluating Regressions
  10. Compilation caching trade-off
  11. Compare all build types
  12. Per-change vs. cumulative
  13. Best-practice settings are not revert candidates
  14. When to recommend revert (speculative changes only)
Ships with 4 files
  • references/build-settings-best-practices.md
  • references/fix-patterns.md
  • references/recommendation-format.md
  • scripts/benchmark_builds.py
Commands it runs
python3 scripts/benchmark_builds.py \
More from Xcode-Build-Optimization-Agent-Skill
All skills →
About this skill
What does the xcode-build-fixer skill do?

Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level compilation fixes, or SPM restructuring that was recommended by an analysis skill.

How do I install it?

Run `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-build-fixer --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.

Keep going