Xcode project auditor
Swift-focused AI agent skills for iOS and macOS: build, debug, simulator, SwiftUI, Xcode, App Store workflows. Part of Plug'n Skills.
npx -y skills add Xopoko/build-swift-apps --skill xcode-project-auditorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Audit Xcode project configuration, schemes, build settings, target dependencies, run scripts, module maps, explicit modules, and fixed build overhead with approval gates.
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, andExtractAppIntentsMetadatatiming- CocoaPods presence: if
PodfileorPods.xcodeprojexists, 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 937 of the 1,487 authors here whose files we hold, read 2026-08-07
- Fetch latest guidelines before each reviewin 43 of 937, across 3 files
- Group findings by severityin 43 of 937
- Check files against all fetched rulesin 42 of 937, across 2 files
- Output findings in terse file:line formatin 41 of 937, across 3 files
- Ask user which files to review if none specifiedin 41 of 937, across 3 files
- Read specified files or prompt user for filesin 39 of 937, across 1 file
- Generate the audit reportin 33 of 937, across 30 files
- Assign a severity to every findingin 25 of 937
- Run automated accessibility scansin 23 of 937, across 13 files
- Output a markdown audit reportin 22 of 937
- Map findings to WCAG criteriain 20 of 937, across 10 files
- Confirm audit scopein 19 of 937, across 9 files
Said here and by no other author read
- Review scheme build order and target dependencies
- Review run script inputs and outputs
- Review DerivedData churn and fixed rebuild overhead
- Review parallelization and explicit module settings
- Recommend SPM migration if CocoaPods exists
- Include a build settings checklist for Debug and Release
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.