spm-build-analysis

1# SPM Build Analysis
2 
3Use this skill when package structure, plugins, or dependency configuration are likely contributing to slow Xcode builds.
4 
5## Core Rules
6 
7- Treat package analysis as evidence gathering first, not a mandate to replace dependencies.
8- Separate package-graph issues from project-setting issues.
9- Do not rewrite package manifests or dependency sources without explicit approval.
10 
11## What To Inspect
12 
13- `Package.swift` and `Package.resolved`
14- local packages vs remote packages
15- package plugin and build-tool usage
16- binary target footprint
17- dependency layering, repeated imports, and potential cycles
18- build logs or timing summaries that show package-related work
19 
20## Verification Before Recommending
21 
22Before including any local package in a recommendation, verify that it is actually part of the project's dependency graph. A `Vendor/` directory may contain packages that are not linked to any target.
23 
24- Check `project.pbxproj` for `XCLocalSwiftPackageReference` entries that reference the package path.
25- Check `XCSwiftPackageProductDependency` entries to confirm the package's product is linked to at least one target.
26- If a local package exists on disk but is not referenced in the project, do not include it in build-time recommendations.
27 
28When recommending version pins for branch-tracked dependencies:
29 
30- Use the helper script to scan all branch-pinned dependencies at once:
31  ```bash
32  python3 scripts/check_spm_pins.py --project App.xcodeproj
33  ```
34…