Download for MacApple silicon, macOS 14+
Skill

spm-build-analysis

@avdlee Updated 2026-09-14

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.

agentagent-skillsiosios-developmentskillsxcode

Install

With your agent

Install OMGSkills skill "avdlee/xcode-build-optimization-agent-skill:spm-build-analysis" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/AvdLee/Xcode-Build-Optimization-Agent-Skill /tmp/Xcode-Build-Optimization-Agent-Skill && ln -s /tmp/Xcode-Build-Optimization-Agent-Skill/skills/spm-build-analysis ~/.claude/skills/spm-build-analysis

From README

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