Spm Build Analysis

avdlee/xcode-build-optimization-agent-skill

Points at your SPM dependencies when Xcode builds feel slow and you suspect packages are the culprit. It digs through Package.swift, checks for branch-pinned dependencies that should be tagged, flags build plugins adding overhead, and spots configuration drift that forces duplicate module builds. The verification rules are smart: it won't blame a package in your Vendor folder unless it's actually linked in the project file. One thing worth knowing is the modular SDK caveat. Splitting a monolithic package into separate targets doesn't automatically speed things up because you're trading one big compile for many small ones. Always benchmark before migrating for performance reasons.

skills.sh installs: 3.5K
GitHub stars: 1.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add avdlee/xcode-build-optimization-agent-skill --skill spm-build-analysis --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

SKILL.md on GitHub