swiftpm-macos

Savant verdict: Analyzed

Scanned or evaluated by Savant; not yet both passing.

Live evaluation

1 pass · 1 investigate · 5 fail across 7 cases. Jev accepted 7 of 14 LLM-drafted cases. Drafted and run by nvidia/nemotron-3-super-120b-a12b, validated and scored by jev-latest.

• I have a SwiftPM package with an executable product named 'Calculator' and a library product. Please build and run it.positive case · investigate
• Test the SwiftPM package in this repo. I want to run all tests and see if they pass.positive case · fail
• Build the release version of the 'Server' executable in this SwiftPM package for performance testing.positive case · fail
• Test the networking functionality in this SwiftPM package.edge case · fail
• I think this package has a bug. Can you build and run it to see?edge case · pass
• Create a new Xcode project from this SwiftPM package and configure it for distribution.negative case · fail
• Profile the CPU usage of the SwiftPM executable using Instruments.negative case · fail

Safety (NVIDIA SkillSpector)

0 patterns found

Structure

• No license declaredConfirm you may reuse this skill before importing it into your repository.

SKILL.md

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

# 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