# Xcode Project Analyzer

Audit Xcode project configuration, build settings, scheme behavior, and script phases...

- Repository: https://github.com/AvdLee/Xcode-Build-Optimization-Agent-Skill (1268 stars)
- Category: Mobile
- License: MIT
- Last updated: 2026-09-14
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-project-analyzer -g -a claude-code -y`
Codex: `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-project-analyzer -g -a codex -y`
Cursor: `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-project-analyzer -g -a cursor -y`
Gemini CLI: `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill xcode-project-analyzer -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add AvdLee/Xcode-Build-Optimization-Agent-Skill`

## Description

Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Xcode Project Analyzer

Use this skill for project- and target-level build inefficiencies that are unlikely to be solved by source edits alone.

## Core Rules

- Recommendation-first by default.
- Require explicit approval before changing project files, schemes, or build settings.
- Prefer measured findings tied to timing summaries, build logs, or project configuration evidence.
- Distinguish debug-only pain from release-only pain.

## What To Review

- scheme build order and target dependencies
- debug vs release build settings against the [build settings best practices](references/build-settings-best-practices.md)
- run script phases and dependency-analysis settings
- derived-data churn or obviously invalidating custom steps
- opportunities for parallelization
- explicit module dependency settings and module-map readiness
- "Planning Swift module" time in the Build Timing Summary -- if it dominates incremental builds, suspect unexpected input modification or macro-related invalidation
- asset catalog compilation time, especially in targets with large or numerous catalogs
- `ExtractAppIntentsMetadata` time in the Build Timing Summary -- if this phase consumes significant time, record it as `xcode-behavior` (report the cost and impact, but do not suggest a repo-local optimization unless there is explicit Apple guidance)
- zero-change build overhead -- if a no-op rebuild exceeds a few seconds, investigate fixed-cost phases (script execution, codesign, validation, CopySwiftLibs)
- CocoaPods usage -- if a `Podfile` or `Pods.xcodeproj` exists, CocoaPods is deprecated; recommend migrating to SPM and do not attempt CocoaPods-specific optimizations (see [project-audit-checks.md](references/project-audit-checks.md))
- Task Backtraces (Xcode 16.4+: Scheme Editor > Build > Build Debugging) to diagnose why tasks re-run unexpectedly in incremental builds

## Build Settings Best Practices Audit

The rest: https://github.com/AvdLee/Xcode-Build-Optimization-Agent-Skill/blob/HEAD/skills/xcode-project-analyzer/SKILL.md