axiom-build-debugging

Diagnose iOS build failures and dependency resolution issues for CocoaPods and Swift Package Manager.

Updated Dec 23, 2025
One-click install
npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-build-debugging-pradeepmouli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: axiom-build-debugging
Source: https://github.com/pradeepmouli/swift-template/tree/main/.agents/skills/axiom-build-debugging
Command: npx skills add https://github.com/pradeepmouli/swift-template --skill axiom-build-debugging-pradeepmouli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly identify and diagnose dependency and build configuration issues that block iOS projects, reducing time spent on root-cause analysis.

Core Features & Use Cases

  • Dependency-resolution diagnostics for CocoaPods and Swift Package Manager
  • Build error analysis for common issues like "Multiple commands produce" and framework version conflicts
  • Reproducible diagnostic workflows and environment guidance for local and CI environments

Quick Start

Execute a step-by-step diagnostic workflow to identify whether the issue is related to dependency graphs, build settings, or environment mismatches.

Frequently Asked Questions about axiom-build-debugging

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

FAQPage Schema
How do I diagnose iOS build failures related to dependency resolution in Xcode?

Yes, this diagnostic workflow compares local and CI environments to pinpoint mismatches causing dependency resolution failures, providing specific environment guidance to reproduce and resolve Xcode build issues across both setups.

What is the best way to fix CocoaPods and Swift Package Manager version conflicts?

The best way to fix dependency version conflicts is by performing a dependency graph analysis that identifies overlapping requirements in CocoaPods and Swift Package Manager, then applying targeted diagnostic workflows to resolve the conflicting framework versions.

Why does my Xcode build fail with multiple commands producing the same output?

Xcode build failures like multiple commands producing the same output typically stem from framework version conflicts or misconfigured build settings, which you can isolate by analyzing dependency resolution paths and applying reproducible diagnostic workflows.

Does this work for diagnosing iOS dependency issues in both local and CI environments?

Yes, this diagnostic workflow compares local and CI environments to pinpoint mismatches causing dependency resolution failures, providing specific environment guidance to reproduce and resolve Xcode build issues across both setups.