Help us improve
Share bugs, ideas, or general feedback.
From Build Swift Apps
Analyzes Swift Package Manager dependencies, plugins, module variants, branch pins, package graph shape, macros, binary targets, and CI/local build overhead that slow Xcode builds.
npx claudepluginhub xopoko/build-swift-apps --plugin build-swift-appsHow this skill is triggered — by the user, by Claude, or both
Slash command
/build-swift-apps:swiftpm-build-inspectorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Gather evidence before recommending package changes. Do not edit manifests/dependencies without explicit approval.
Analyzes SPM dependencies, plugins, module variants, and CI overhead slowing Xcode builds. Detects cycles, oversized modules, config drift, and graph issues hurting clean/incremental perf.
Audits Xcode project configuration, build settings, schemes, target dependencies, run scripts, module maps, and explicit modules to find build inefficiencies and recommend fixes with approval gates.
Provides a checklist for code reviews covering functionality, security, performance, maintainability, tests, and quality. Use for pull requests, audits, team standards, and developer training.
Share bugs, ideas, or general feedback.
Gather evidence before recommending package changes. Do not edit manifests/dependencies without explicit approval.
Package.swift, Package.resolvedBefore recommending a local package, prove it is in the project graph: check XCLocalSwiftPackageReference and XCSwiftPackageProductDependency in project.pbxproj. Ignore on-disk packages that are not linked.
For branch-pinned dependencies:
python3 scripts/check_spm_pins.py --project App.xcodeproj
If tags exist, recommend tag pins when appropriate; otherwise recommend a revision hash for determinism. Distinguish intentional branch tracking from missing-tag upstreams.
@_exported importswift-syntax cascadesModular SDK migrations do not automatically speed builds. Compare SwiftCompile, SwiftEmitModule, and ScanDependencies task counts and benchmark before recommending for performance; note when the benefit is import hygiene/API surface rather than wait time.
If the same module appears multiple times in timing output, investigate option/variant drift before source shaving.
For each finding include evidence, affected package/plugin, clean vs incremental impact, CI impact, estimated wait-time impact, and approval requirement. If the bottleneck is not package-related, hand off to xcode-project-auditor or xcode-compile-profiler.
References: references/spm-analysis-checks.md, ../../shared/build-optimization/references/recommendation-format.md, build-optimization-sources.md.