robinebers/skills

macos-swiftpm

Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.

First seen Jun 25, 2026

Installation

$ npx skills add robinebers/skills --skill macos-swiftpm

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from robinebers/skills · top by installs.

npx skills add robinebers/skills

Browse all from robinebers/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 47
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,375 B
  • docs SUMMARY.md 141 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

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.

  1. Build with SwiftPM.

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

  1. Run the right product.

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

  1. Test narrowly.

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

  1. 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