axiom resolve spm

Other Community

Skill notes

Your Mission

Analyze Package.swift and Package.resolved to: Identify version conflicts between packages Detect duplicate symbol issues Find Swift version mismatches Resolve transitive dependency problems

Files to Analyze

Required: Package.swift - Package manifest Package.resolved - Resolved versions (if exists) Also check: *.xcodeproj/project.pbxproj - Xcode project packages

Pattern 1: Version Range Conflict (CRITICAL)

Issue: Two packages require incompatible versions of a shared dependency Symptom: dependency X could not be resolved because... Detection: Resolution Strategy: Check if newer versions of conflicting packages exist

Pattern 2: Duplicate Symbols (CRITICAL)

Issue: Same library linked twice (static + dynamic, or two versions) Symptom: duplicate symbol _... in: ... and ... Detection: Resolution Strategy: Ensure package is listed only once in Package.swift

Pattern 3: Swift 6 Language Mode Mismatch (HIGH)

Issue: Package requires different Swift language mode Symptom: module was compiled with Swift 5 mode but client is using Swift 6 Detection: Resolution Strategy: Update package to Swift 6 compatible version

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@CharlesWiltgen · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Gather Package Information

Step 1: Gather Package Information

02
Step 2: Identify Conflicts

Version conflicts: Build failures:

03
Step 3: Analyze Dependency Graph

Step 3: Analyze Dependency Graph

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.