SPM Build Analysis

Use this skill when package structure, plugins, or dependency configuration are likely contributing to slow Xcode builds.

Core Rules

• Treat package analysis as evidence gathering first, not a mandate to replace dependencies.
• Separate package-graph issues from project-setting issues.
• Do not rewrite package manifests or dependency sources without explicit approval.

What To Inspect

• Package.swift and Package.resolved
• local packages vs remote packages
• package plugin and build-tool usage
• binary target footprint
• dependency layering, repeated imports, and potential cycles
• build logs or timing summaries that show package-related work

Verification Before Recommending

Before 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.

• Check project.pbxproj for XCLocalSwiftPackageReference entries that reference the package path.
• Check XCSwiftPackageProductDependency entries to confirm the package's product is linked to at least one target.
• If a local package exists on disk but is not referenced in the project, do not include it in build-time recommendations.

When recommending version pins for branch-tracked dependencies:

• Use the helper script to scan all branch-pinned dependencies at once:

  python3 scripts/check_spm_pins.py --project App.xcodeproj
  

  This checks git ls-remote --tags for each branch-pinned package and reports which have tags available for pinning.
• If no tags exist, recommend pinning to a specific commit revision hash for determinism instead.
• Note which packages are branch-pinned because the upstream simply has no tags, versus packages that have tags but are intentionally tracking a branch.

Focus Areas