mcpField
S
swiftpm-macos

swiftpm-macos

github.com/openaiDevelopment7.6k59 installsUpdated 3w ago
Repository

About swiftpm-macos

A skill for macOS Swift developers working from Package.swift, with a workflow for inspecting products and building, running, and testing through SwiftPM.

Key features

  1. 01Inspect Package.swift and products
  2. 02Build with swift build
  3. 03Run executables with swift run
  4. 04Test with swift test
  5. 05Classify and summarize common failures

Use cases

  1. 01Build a SwiftPM macOS package
  2. 02Run an executable product in a package
  3. 03Test a specific test target
  4. 04Diagnose dependency, linker, or runtime issues

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/openai/plugins --skill swiftpm-macos

After installing, type/swiftpm-macosin Claude Code to confirm it loaded.

Bundled filesagents/openai.yaml

Details

From the project README

SwiftPM for macOS

Quick Start

Use this skill when Package.swift is the primary entrypoint or when SwiftPM is the fastest path to a reproducible result.

Workflow

  1. Inspect the package.

    • Read Package.swift.
    • Identify executable, library, and test products.

  2. Build with SwiftPM.

    • Use swift build by default.
    • Use release mode only when the user explicitly needs it.

  3. Run the right product.

    • Use swift run <product> when an executable exists.
    • If multiple executables exist, explain the default choice.

  4. Test narrowly.

    • Use swift test.
    • Apply filters when a specific test target or case is known.

  5. Summarize failures.

    • Module/import resolution
    • Package graph or dependency issue
    • Linker failure
    • Runtime failure
    • Test regression

Guardrails

  • Prefer SwiftPM over Xcode when both exist and the package path is clearly simpler.
  • Do not assume an app bundle exists in a pure package workflow.
  • Explain when the package is library-only and therefore not directly runnable.

Output Expectations

Provide:

  • the package products you found
  • the command you ran
  • whether build, run, or test succeeded
  • the top blocker if not

Comments

Markdown supported