spm-build-analysis
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.
npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill spm-build-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 th
- Core Rules
- What To Inspect
- Verification Before Recommending
- Focus Areas
- Modular SDK Migration Caveat
- Explicit Module Dependency Angle
- Reporting Format
- Additional Resources
python3 scripts/check_spm_pins.py --project App.xcodeproj
What does the spm-build-analysis skill do?
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.
How do I install it?
Run `npx skills add AvdLee/Xcode-Build-Optimization-Agent-Skill --skill spm-build-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From AvdLee/Xcode-Build-Optimization-Agent-Skill, a repository with 1,193 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.