test-package

Execute isolated SwiftPM build and test cycles for specific Swift packages.

1|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/adamayoung/popcorn --skill test-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-package
Source: https://github.com/adamayoung/popcorn/tree/main/.claude/skills/test-package
Command: npx skills add https://github.com/adamayoung/popcorn --skill test-package

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables targeted testing of individual Swift packages within the repository, avoiding the overhead of running the entire application test suite when only a specific module needs verification.

Core Features & Use Cases

  • Isolated Testing: Executes build and test commands for specific Context, Adapter, Core, or Platform packages.
  • Safety Checks: Automatically identifies and gates feature packages that contain snapshot tests or UIKit dependencies, preventing build failures in the SwiftPM CLI.
  • Resource Management: Ensures clean-up of build artifacts to prevent simulator-install conflicts in subsequent full-app test runs.

Quick Start

Ask the assistant to test the Swift package located at the specified path using the test-package skill.

Frequently Asked Questions about test-package

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

FAQPage Schema
How do I run isolated tests for a specific Swift package without triggering the full app suite?

Isolated Swift package testing executes targeted build and test cycles for specific directories using the SwiftPM CLI, avoiding the overhead of running the entire application test suite for a single module.

Why do my SwiftPM tests fail for packages with snapshot tests or UIKit dependencies?

SwiftPM CLI builds fail with snapshot tests or UIKit dependencies because this skill enforces safety gates that automatically identify and skip these feature packages to prevent build failures.

How do I test Context, Adapter, Core, or Platform packages using SwiftPM?

Testing Context, Adapter, Core, or Platform packages involves executing isolated SwiftPM build and test commands targeting those specific directory structures within the repository.

Do I need to clean up SwiftPM build artifacts before running full app tests?

Mandatory cleanup of SwiftPM build artifacts is required to maintain environment integrity and prevent simulator-install conflicts during subsequent full-app test runs.

What is the best way to verify a single Swift package module in a large repository?

Targeted SwiftPM CLI testing is the best way to verify a single module, executing isolated build cycles while enforcing safety gates for incompatible packages and cleaning up build artifacts.

Does the test-package skill work with feature packages containing UI dependencies?

The skill does not work with feature packages containing UI dependencies, as it automatically identifies and gates packages with snapshot tests or UIKit dependencies to prevent SwiftPM CLI failures.