swift-package-workflow

Route broad Swift Package Manager requests to narrower build or testing workflows.

6|Updated Apr 9, 2026

Search Tags:#automation #workflow #routing #xcode #swiftpm #swift-package

Ready to run

npx skills add https://github.com/gaelic-ghost/socket --skill swift-package-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: swift-package-workflow
Source: https://github.com/gaelic-ghost/socket/tree/main/plugins/apple-dev-skills/skills/swift-package-workflow
Command: npx skills add https://github.com/gaelic-ghost/socket --skill swift-package-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Scheduling and routing for broad or legacy Swift Package Manager requests can be confusing when a repository uses a mixed root with Xcode markers. This surface funnels such requests to the appropriate narrower skills (swift-package-build-run-workflow or swift-package-testing-workflow) while preserving the mixed-root handoff boundaries.

Core Features & Use Cases

Compatibility routing: Detects broad SwiftPM prompts and routes to the most suitable concrete workflow.
Mixed-root awareness: Preserves Xcode-related handoff boundaries to avoid unintended mutations or surface conflicts.
Context provisioning: Returns routing context and recommended next steps to support downstream skills.

Quick Start

Describe a broad SwiftPM request to route it to the correct narrower workflow.

Frequently Asked Questions about swift-package-workflow

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

FAQPage Schema

How do I route Swift Package Manager requests in a mixed-root repository?▼

To route Swift Package Manager requests in a mixed-root repository, this Skill detects broad SwiftPM prompts and directs them to the correct narrower workflow while preserving Xcode-related handoff boundaries to avoid unintended mutations.

When do I need compatibility routing for SwiftPM workflows?▼

You need compatibility routing for SwiftPM workflows when handling broad or legacy Swift Package Manager requests that require handoff between swift-package-build-run-workflow and swift-package-testing-workflow in mixed-root repositories.

What is the best way to handle legacy Swift Package Manager prompts with Xcode markers?▼

The best way to handle legacy Swift Package Manager prompts with Xcode markers is to funnel them through a routing surface that enforces compatibility routing and captures escalation rules for Xcode-aware surfaces.

Does this routing workflow support handoff to Xcode build and testing workflows?▼

Yes, this routing workflow supports mixed-root handoff boundaries to xcode-build-run-workflow or xcode-testing-workflow, capturing escalation rules for Xcode-aware surfaces when needed to prevent surface conflicts.

Why does my broad SwiftPM prompt need routing context before execution?▼

Your broad SwiftPM prompt needs routing context because this Skill provisions context and recommended next steps to support downstream skills, ensuring the correct narrower workflow executes the request accurately.

Can I use this to route SwiftPM requests without triggering Xcode surface conflicts?▼

Yes, you can use this to route SwiftPM requests without triggering Xcode surface conflicts because it preserves mixed-root handoff boundaries and enforces compatibility routing across swift-package-build-run-workflow and swift-package-testing-workflow.