Xcode project auditor

Skill Xopoko/build-swift-apps/skills/xcode-project-auditor

Audit Xcode project configuration, schemes, build settings, target dependencies, run scripts, module maps, explicit modules, and fixed build overhead with approval gates.From its SKILL.md

Install

npx -y skills add Xopoko/build-swift-apps --skill xcode-project-auditor

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.5 KB, 489 tokens by cl100k_base, as published. Nobody here has run it

Xcode Project Auditor

Use for project- and target-level build inefficiencies. Recommend first and require explicit approval before changing projects, schemes, or build settings.

Review

scheme build order and target dependencies
Debug vs Release performance settings from ../../shared/build-optimization/references/build-settings-best-practices.md
run script inputs/outputs, .xcfilelist, dependency analysis, and timestamp-changing tools
DerivedData churn, custom steps, fixed no-op rebuild overhead, codesign, validation, CopySwiftLibs
parallelization opportunities, explicit module settings, module maps, DEFINES_MODULE, and self-contained headers
Planning Swift module, asset catalog compilation, and ExtractAppIntentsMetadata timing
CocoaPods presence: if Podfile or Pods.xcodeproj exists, recommend SPM migration and avoid CocoaPods-specific optimization
Xcode 16.4+ Task Backtraces for tasks that rerun unexpectedly

Required Checklist

Every audit includes a build settings checklist for Debug and Release using [x]/[ ]. Scope is build performance only; do not flag language-migration settings such as SWIFT_STRICT_CONCURRENCY or SWIFT_UPCOMING_FEATURE_*.

Apple-aligned checks: accurate target dependencies, schemes in Dependency Order, scripts with declared inputs/outputs, .xcfilelist for many files, consistent explicit module settings, and module-map readiness.

Typical Wins

Skip debug-time scripts that only matter in release, add script guards and dependency metadata, remove accidental serial bottlenecks, align settings that create extra module variants, stop formatters/linters from touching unchanged files, split huge asset catalogs into resource bundles, and use Task Backtraces to find the input that triggers invalidation.

Output

For each issue include evidence, scope, whether it affects clean/incremental/both, estimated impact, and approval requirement. If evidence points to package graph or build plugins, read and hand off to swiftpm-build-inspector.

Resources

references/project-audit-checks.md
../../shared/build-optimization/references/build-settings-best-practices.md
../../shared/build-optimization/references/recommendation-format.md
../../shared/build-optimization/references/build-optimization-sources.md

What ships with it: 1 file

8.3 KB alongside SKILL.md

references/

project-audit-checks.md8.3 KB

Gives 0 of the 12 instructions most audit compliance skills give in 489 tokens

Counted across 960 of the 1,589 authors here whose files we hold, read 2026-09-06

Read product marketing context before asking questionsin 29 of 960, across 11 files
Rank findings by severityin 29 of 960, across 22 files
Generate audit reportin 22 of 960
Run the audit scriptin 20 of 960, across 19 files
Generate a prioritized action plan reportin 19 of 960, across 11 files
Ensure one H1 per pagein 15 of 960, across 5 files
Ensure sitemap exists and is accessiblein 14 of 960, across 4 files
Verify alt text on all imagesin 12 of 960, across 3 files
Determine the audit scope before startingin 12 of 960, across 4 files
Verify important pages allowed in robots.txtin 11 of 960, across 2 files
Detect business type from homepage signalsin 11 of 960, across 7 files
Delegate specialized tasks to subagentsin 11 of 960, across 7 files

Said here and by no other author read

Confirm execution context is macOS before invoking Apple-only binaries
Require explicit approval before changing projects or schemes
Review scheme build order and target dependencies
Review Debug versus Release performance settings
Review run script inputs and outputs
Review parallelization opportunities and explicit module settings

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.