spm-build-analysis

Analyze Swift Package Manager dependencies and build logs for Xcode build bottlenecks.

7|8|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/omarshahine/Apple-PIM-Agent-Plugin --skill spm-build-analysis-omarshahine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spm-build-analysis
Source: https://github.com/omarshahine/Apple-PIM-Agent-Plugin/tree/main/.claude/skills/spm-build-analysis
Command: npx skills add https://github.com/omarshahine/Apple-PIM-Agent-Plugin --skill spm-build-analysis-omarshahine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Swift Package Manager dependencies, plugins, and module configurations can cause slow Xcode builds due to complex graphs, plugin overhead, and drift across targets. This skill analyzes dependency graphs, plugin usage, and CI overhead to identify bottlenecks and guide optimizations.

Core Features & Use Cases

  • Dependency graph analysis: map packages, plugins, and targets to identify slow paths.
  • Duplication and drift detection: uncover repeated module builds and configuration drift across targets.
  • CI/build-log insights: summarize timing data to guide targeted optimizations.

Quick Start

Analyze your Xcode project to surface SPM-related build bottlenecks and provide actionable recommendations.

Frequently Asked Questions about spm-build-analysis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does Xcode build the same Swift package multiple times for different targets?

Duplicate module builds in Xcode often stem from configuration drift across targets or complex dependency graphs. Analyzing your SPM dependency graph and target configurations uncovers repeated builds and circular dependencies, enabling you to resolve the duplication.

Can I detect circular dependencies in my Swift Package Manager graph?

Yes, you can detect circular dependencies by analyzing your Swift Package Manager dependency graph. Enforcing checks on Package.swift and Package.resolved surfaces circular dependencies and complex graph bottlenecks that slow down Xcode builds.

What is the best way to find slow paths in my Swift Package Manager dependency graph?

The best way to find slow paths is by mapping packages, plugins, and targets within your SPM dependency graph. This analysis identifies bottlenecks caused by binary targets and complex dependencies, providing actionable recommendations with validation steps.

Does SPM build analysis work with both local and remote packages?

Yes, SPM build analysis works with projects using both local and remote packages, binary targets, and build plugins. It enforces checks across Package.swift, Package.resolved, and project.pbxproj to surface actionable recommendations with guardrails.