Diagnose Swift Package Manager dependency conflicts and build errors.
npx skills add https://github.com/DengNaichen/Stet --skill axiom-resolve-spm
Please help me install this Agent Skill. Skill: axiom-resolve-spm Source: https://github.com/DengNaichen/Stet/tree/main/.agents/skills/axiom-resolve-spm Command: npx skills add https://github.com/DengNaichen/Stet --skill axiom-resolve-spm
This Skill resolves complex Swift Package Manager dependency issues, including version conflicts, duplicate symbols, and Swift language mode mismatches that prevent successful builds.
Use the axiom-resolve-spm skill to analyze the current directory and identify the cause of the build failure.
High-intent search queries and answers about installing and using this skill.
Duplicate symbol linker errors in Xcode often stem from Swift Package Manager transitive dependency collisions. Analyzing your Package.swift and Package.resolved files pinpoints the exact dependency causing the duplicate symbol issue and suggests necessary version adjustments.
To resolve Swift Package Manager version conflicts, you must identify version range incompatibilities within your dependency graph. This involves analyzing your dependency files to pinpoint the exact package causing the collision and applying the suggested version adjustments.
A no such module error during Swift package integration typically indicates a dependency graph failure or Swift language mode mismatch. Diagnosing the Package.resolved file identifies the specific dependency causing the integration failure and platform compatibility issues.
Yes, you can fix Swift language mode mismatches and macro build failures in macOS development. Resolution strategies apply to iOS and macOS environments to correct platform version mismatches and align Swift language modes for successful builds.
The best way to diagnose transitive dependency issues is to analyze the dependency graph for version range incompatibilities. This process identifies the exact dependencies causing integration failures and provides actionable steps to fix platform version mismatches.
To fix SPM dependency conflicts when a Swift package fails to build, analyze the current directory's Package.swift and Package.resolved files. This identifies the dependency causing the collision and suggests the necessary version adjustments for resolution.
gaelic-ghostBuild and run Swift packages using SwiftPM commands.
diegopetrucciRun Swift unit tests across iOS simulators with xcodebuild.
PallepadehatReview and remediate Swift 6.2+ concurrency issues with actor isolation and Sendable safety.
TheBushidoCollectiveResolve Maven dependency conflicts and optimize dependency trees in Java projects.
