Agent skill

Xcsift

by ldomaradzki in ldomaradzki/xcsift

Use xcsift for all Swift and Xcode build commands. An agent skill from ldomaradzki/xcsift.

MITAuto-check passedMobile

Install Xcsift

skills CLI
$ npx skills add ldomaradzki/xcsift --skill xcsift -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ldomaradzki/xcsift xcsift --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ldomaradzki/xcsift.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/codex .claude/skills/xcsift && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
xcsift
GitHub stars
489
Token cost
~1.2k tokens
SKILL.md length
360 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Use xcsift for all Swift and Xcode build commands. An agent skill from ldomaradzki/xcsift.

  • Tasks that involve iOS development
  • SKILL.md covers When to Use, When Not to Use, Usage Pattern and Key Flags, plus 3 more sections
  • Calls xcodebuild, swift and brew
  • Tasks that involve Test coverage

What it does

Xcsift is an agent skill from ldomaradzki/xcsift. Use xcsift for all Swift and Xcode build commands. Pipe xcodebuild build, xcodebuild test, swift build, swift test through xcsift for structured TOON output with compile errors, warnings, test failures, code coverage, slow tests, and build timing. Essential for parsing Xcode build output, diagnosing compile errors, analyzing test results, and measuring code coverage in any Swift or Xcode project.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Mobile, covering iOS development and Test coverage. It works with Xcode. The repository describes itself as: A Swift command-line tool that parses xcodebuild output into token-efficient JSON for coding agents. The licence is MIT.

When your agent uses it

  • Tasks that involve iOS development
  • Tasks that involve Test coverage

Example prompts

  • “/xcsift”

What it can do on your machine

Read from SKILL.md and the folder at commit c219e12. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • xcodebuild
    • swift
    • brew

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Xcsift loads about 1.2k tokens when it runs. Until then it costs about 102 tokens; SKILL.md has 360 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~102
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ldomaradzki/xcsift at commit c219e12, republished under its MIT licence (© ldomaradzki). 360 words, ~1,217 tokens.

Download SKILL.mdSave it as .claude/skills/xcsift/SKILL.md (or your agent's skills folder).
name
xcsift
description
Use xcsift for all Swift and Xcode build commands. Pipe xcodebuild build, xcodebuild test, swift build, swift test through xcsift for structured TOON output with compile errors, warnings, test failures, code coverage, slow tests, and build timing. Essential for parsing Xcode build output, diagnosing compile errors, analyzing test results, and measuring code coverage in any Swift or Xcode project.

xcsift - Xcode Build Output Formatter

xcsift parses and formats xcodebuild/SPM output into token-efficient TOON format optimized for LLM consumption. It extracts compile errors, warnings, test failures, code coverage, and build timing from verbose Xcode output.

When to Use

Always pipe through xcsift when running:

  • xcodebuild build / xcodebuild test
  • swift build / swift test
  • Any command that produces Xcode/SPM build output

When Not to Use

Informational commands print an answer, not a build log. xcsift discards that answer, so run them directly:

  • xcodebuild -version / -usage / -help
  • xcodebuild -list / -showsdks / -showdestinations / -showTestPlans / -showBuildSettings
  • xcodebuild -find-executable / -find-library / -create-xcframework
  • swift build --show-bin-path, swift test --list-tests, and any --help or --version command

Usage Pattern

Always redirect stderr and use TOON format:

bash
# Build
xcodebuild build 2>&1 | xcsift -f toon
swift build 2>&1 | xcsift -f toon

# Test
swift test 2>&1 | xcsift -f toon
xcodebuild test 2>&1 | xcsift -f toon

# With warnings
xcodebuild build 2>&1 | xcsift -f toon -w

# With code coverage
swift test --enable-code-coverage 2>&1 | xcsift -f toon -c
xcodebuild test -enableCodeCoverage YES 2>&1 | xcsift -f toon -c

# With detailed per-file coverage
swift test --enable-code-coverage 2>&1 | xcsift -f toon -c --coverage-details

# With executable targets
xcodebuild build 2>&1 | xcsift -f toon -e

# Strict CI mode (fail on warnings or errors)
xcodebuild build 2>&1 | xcsift -f toon -W -E

# Slow test detection
swift test 2>&1 | xcsift -f toon --slow-threshold 1.0

# Build info (per-target phases, timing, dependencies)
xcodebuild build 2>&1 | xcsift -f toon --build-info

Key Flags

FlagDescription
-f toonTOON format (30-60% fewer tokens than JSON)
-wShow detailed warnings list
-WTreat warnings as errors (Werror)
-qQuiet mode (no output on clean success)
-cInclude code coverage summary
--coverage-detailsPer-file coverage breakdown (use with -c)
-eInclude executable targets
-EExit with non-zero code on build failure
--build-infoPer-target phases, timing, and dependencies
--slow-threshold NFlag tests slower than N seconds
--config PATHUse custom config file (default: .xcsift.toml)
--initGenerate .xcsift.toml template in current directory
Show full SKILL.md (160 more words)Show less

Interpreting TOON Output

TOON uses indentation-based structure with tabular arrays:

toon
status: failed
summary:
  errors: 1
  warnings: 3
  failed_tests: 2
  passed_tests: 10
  build_time: 12.4s
  test_time: 5.2s
errors[1]{file,line,message}:
  main.swift,15,"use of undeclared identifier 'foo'"
warnings[3]{file,line,message,type}:
  Parser.swift,20,"unused variable 'result'",compile
  View.swift,42,"Publishing changes from background threads",swiftui
  Util.swift,10,"Custom warning message",runtime
failed_tests[2]{suite,test,file,line,message,duration}:
  MyTests,testExample,MyTests.swift,25,"XCTAssertEqual failed",0.123
  MyTests,testOther,MyTests.swift,30,"XCTAssertTrue failed",0.456

Key patterns:

  • status: succeeded or failed
  • errors[N]{columns}: — tabular array with N items, column names in braces
  • warnings have type: compile, runtime, or swiftui
  • failed_tests include file/line for navigation and duration
  • null values mean the data wasn't available

Troubleshooting

ProblemSolution
No errors shown but build failedAdd 2>&1 to capture stderr
Coverage shows nullAdd --enable-code-coverage (SPM) or -enableCodeCoverage YES (xcodebuild)
"xcsift not found"Install: brew install xcsift or swift build -c release && cp .build/release/xcsift /usr/local/bin/
Coverage for wrong targetxcsift auto-filters to tested target; use --coverage-path to override
Config not loadingCheck .xcsift.toml in CWD or ~/.config/xcsift/config.toml

Important

  • Always use 2>&1 to capture stderr (compiler errors and warnings go to stderr)
  • TOON format reduces tokens by 30-60% compared to raw xcodebuild output
  • When running build commands, always add | xcsift -f toon to the end
  • Flaky test detection is automatic (no flag needed) — detects tests that both pass and fail

© ldomaradzki, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/codex of ldomaradzki/xcsift.

Open the folder on GitHubat commit c219e12

Compare with similar skills

Xcsift next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Xcsift compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Xcsift this skillldomaradzki/xcsift489—~1.2kAutomated safety check: PassMIT
Coverage Reportn0an/VivaDicta131—~1.2kAutomated safety check: PassMIT
Xcode Syncsteipete/agent-scripts7.3k—~2.1kAutomated safety check: NotesMIT
Swift Testingdpearson2699/swift-ios-skills1.2k—~2.8kAutomated safety check: PassCustom licence
Apple History Utilitiespdparchitect/noodle151—~149Automated safety check: PassApache-2.0
Performance Profilingnirholas/three.ws2271 repos~1.5kAutomated safety check: PassApache-2.0

Similar skills

  • Coverage Report

    n0an/VivaDicta

    Measure VivaDicta test code coverage from the terminal. An agent skill from n0an/VivaDicta.

    131 GitHub stars~1.2k tokensUpdated 3 days ago
    Testing & QAAuto-check passed
  • Xcode Sync

    steipete/agent-scripts

    Xcode fleet sync: signed archives, compatibility, install, selection, first launch.

    7.3k GitHub stars~2.1k tokensUpdated 4 days ago
    MobileAuto-check: notes
  • Swift Testing

    dpearson2699/swift-ios-skills

    Writes and migrates Swift Testing framework tests with @Test, @Suite, expect, require, confirmation, traits, withKnownIssue, Attachment.record, processExitsWith exit tests and capture lists…

    1.2k GitHub stars~2.8k tokensUpdated 2 mo ago
    MobileAuto-check passed
  • Apple History Utilities

    pdparchitect/noodle

    Upkeep of the Apple utilities copied into NoodleAppleRuntime.

    151 GitHub stars~149 tokensUpdated yesterday
    MobileAuto-check passed
  • Performance Profiling

    nirholas/three.ws

    Guide performance profiling for Apple platform apps with Instruments, Xcode diagnostics, and MetricKit.

    227 GitHub starsUsed in 1 repo~1.5k tokens
    MobileAuto-check passed
  • Sfsymbol Generator

    sundial-org/awesome-openclaw-skills

    Generate an Xcode SF Symbol asset catalog .symbolset from an SVG.

    663 GitHub stars~429 tokensUpdated 7 mo ago
    MobileAuto-check passed

Works with

Categories

Questions about Xcsift

What does Xcsift do?

Use xcsift for all Swift and Xcode build commands. An agent skill from ldomaradzki/xcsift. Xcsift is an agent skill from ldomaradzki/xcsift. Use xcsift for all Swift and Xcode build commands.

When should I use Xcsift?

Xcsift fits situations like: tasks that involve iOS development; tasks that involve Test coverage.

How do I install Xcsift in Claude Code?

Run `npx skills add ldomaradzki/xcsift --skill xcsift -a claude-code`. Or copy the skill folder (plugins/codex in ldomaradzki/xcsift) into .claude/skills/xcsift in your project. Claude Code loads it when a task matches its description.

How do I install Xcsift in Codex?

Run `npx skills add ldomaradzki/xcsift --skill xcsift -a codex`. Or copy the skill folder (plugins/codex in ldomaradzki/xcsift) into .agents/skills/xcsift in your project. Codex loads it when a task matches its description.

Can I use Xcsift in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ldomaradzki/xcsift --skill xcsift -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/xcsift, .gemini/skills/xcsift, .github/skills/xcsift and .opencode/skills/xcsift in your project.

What does Xcsift need to run?

Going by SKILL.md and its folder, Xcsift needs the command-line tools its instructions call (xcodebuild, swift and brew).

Does Xcsift access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Xcsift safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Xcsift use?

Xcsift is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Xcsift use?

About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Xcsift?

Skills that share tags, products or a category with Xcsift: Coverage Report (n0an/VivaDicta, 131 stars), Xcode Sync (steipete/agent-scripts, 7.3k stars), Swift Testing (dpearson2699/swift-ios-skills, 1.2k stars) and Apple History Utilities (pdparchitect/noodle, 151 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Xcsift?

ldomaradzki (a GitHub user) maintains it in ldomaradzki/xcsift, which has 489 GitHub stars. The repository was last updated on October 4, 2026.

Source: ldomaradzki/xcsift on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.