swiftpm-macos
Build, run, and test SwiftPM macOS packages and executables. Use when the repo is package-first or has no Xcode project.
Savant verdict: Analyzed
Scanned or evaluated by Savant; not yet both passing.
Live evaluation
Not evaluated yet. Workspaces can request a live evaluation.
Safety (NVIDIA SkillSpector)
Risk score
0/100
Recommendation
CAUTION
Severity
LOW
Savant decision
Passed (low risk)
SkillSpector rated it CAUTION, but its risk score is below 20/100, so Savant's policy passes it. Its findings are still listed for review. SkillSpector 2.12.0, static analysis.
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