Peekie
Let your agent parse Xcode .xcresult bundles in CI or locally for tests, failures, coverage, and attachments without hand-reading Xcode’s UI.
Overview
Peekie is a plugin marketplace for the Ship phase that teaches coding agents when and how to use the peekie CLI to parse Xcode .xcresult bundles for tests, warnings, errors, coverage, and attachments.
What is this marketplace?
- Umbrella peekie skill plus five sub-skills: peekie-tests, peekie-warnings, peekie-errors, peekie-coverage, peekie-attach
- Focused on Xcode .xcresult bundles, Swift, Swift Testing, and CI-friendly consumption of test artifacts
- Fully qualified test names and structured extraction for downstream tooling
- JSON output designed for jq pipelines and SonarQube-style reports
- Clear when-to-reach-for-peekie guidance so agents pick the right subcommand per task
- Marketplace lists 1 plugin (peekie v1.0.0) with an umbrella skill and 5 named subcommand skills
- Documented sub-skills: peekie-tests, peekie-warnings, peekie-errors, peekie-coverage, peekie-attachments
Community signal: 25 GitHub stars.
What problem does it solve?
Xcode test and CI outcomes live inside .xcresult bundles that agents cannot interpret reliably without a dedicated CLI workflow and command-specific guidance.
Who is it for?
Indie and solo builders on Xcode who archive .xcresult from local runs or CI and want Claude to debug failures, scan warnings, or pull coverage without manual Xcode clicking.
Skip if: Teams that do not use Xcode or Apple toolchains, or projects that only need generic non-Apple test runners with no .xcresult artifacts.
What do I get? / Deliverables
After you add the peekie plugin, your agent can call the right peekie subcommand, return structured JSON for scripts and quality tools, and surface qualified test names, coverage, and attachments from .xcresult files.
- Structured JSON summaries of tests, warnings, errors, coverage, or attachments from a given .xcresult
- Fully qualified test identifiers and extracted attachment paths suitable for follow-up automation
- CI-friendly output compatible with jq filtering and SonarQube-oriented reporting workflows
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Peekie targets post-build verification: extracting signal from Xcode test runs, warnings, and coverage—the core Ship-phase testing and release-readiness loop for Apple platforms. The skill teaches peekie subcommands aimed at test results, errors, warnings, coverage, and attachments, which maps directly to automated testing and result inspection rather than app implementation.
How it compares
An Xcode-focused agent skill pack around the peekie CLI, not a broad MCP server or a general-purpose coding skill.
Common Questions / FAQ
Who is Peekie for?
Peekie is for developers using Xcode and Swift who want AI agents to read .xcresult bundles from tests and CI the same way a human would in the Report navigator—via structured CLI queries.
When should I use Peekie?
Use Peekie whenever you have an .xcresult path after XCTest or Swift Testing runs and you need failures, warnings, errors, coverage, or attachments turned into JSON for triage, scripts, or SonarQube.
How do I add Peekie to my agent?
Install the Peekie plugin from the Skillselion-listed Claude marketplace (dodobrands/Peekie), ensure the Peekie CLI is on your PATH where the agent runs, and point the agent at .xcresult bundles so it can load the umbrella and sub-skills.