agentsclimarketplace

Xcode build debugger

Skill 7vibex/swiftui-developer-kit/.agents/skills/xcode-build-debugger

Codex skill pack for SwiftUI, SwiftData, Xcode debugging, app audits, screenshots, accessibility, Liquid Glass, and App Store release workflows.

Install
npx -y skills add 7vibex/swiftui-developer-kit --skill xcode-build-debugger

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Diagnose Xcode, SwiftUI, iOS, iPadOS, macOS, scheme, simulator, signing, dependency, and build errors using safe project detection and user-approved build/debug workflows.

SKILL.md

1.9 KB, 367 tokens by cl100k_base, as published. Nobody here has run it

Xcode Build Debugger

Diagnose Xcode build issues with safe detection first. Do not build when the command would be long-running, destructive, or ambiguous without user approval.

References

  • references/xcode-build-checklist.md
  • references/scheme-detection-notes.md
  • references/output-contract.md

Prefer targeted detection scripts before reading many project files.

Workflow

  1. Detect .xcodeproj, .xcworkspace, and Package.swift.
  2. List schemes when safe.
  3. Ask for scheme, device, or platform if ambiguous.
  4. Run the approved build or test command.
  5. Parse errors by root cause, not only by last line.
  6. Propose a scoped fix plan.
  7. Verify with the smallest command that proves the fix.

Guardrails

  • Do not clean DerivedData unless the user approves.
  • Do not change signing settings without explaining the risk.
  • Do not build or launch the app when the user requested code-only diagnosis.

Do Not Use When

  • The task is feature design, UI review, persistence audit, App Store readiness, or PR drafting without a build error.
  • The build or launch command would be ambiguous or side-effectful and the user has not approved it.

Done When

  • Project type, scheme, destination, command, and failing error category are identified or marked missing.
  • Root cause is separated from secondary log noise.
  • Output gives a scoped fix plan and the smallest verification command that proves the result.

Output

Use references/output-contract.md.

Follow ../../../docs/skill-quality-standard.md and compare ../../../examples/skill-outputs/xcode-build-debugger-bad-output.md with ../../../examples/skill-outputs/xcode-build-debugger-good-output.md.

What ships with it: 5 files

2.3 KB alongside SKILL.md, 2 of them executable

references/

scripts/

Gives 0 of the 12 instructions most debug triage skills give in 367 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-07

  • Investigate root cause before proposing any fixin 102 of 839, across 67 files
  • Read error messages completelyin 89 of 839, across 49 files
  • Create a failing test case before fixingin 84 of 839, across 46 files
  • Reproduce the issue consistentlyin 82 of 839, across 41 files
  • Change one variable at a timein 82 of 839, across 42 files
  • Check recent changesin 74 of 839, across 36 files
  • Write the regression test before fixingin 74 of 839, across 40 files
  • Fix the root cause not the symptomin 60 of 839, across 45 files
  • Implement a single fix at a timein 59 of 839, across 20 files
  • Trace data flow backward to the sourcein 50 of 839, across 20 files
  • Remove all debug instrumentationin 49 of 839, across 13 files
  • Form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

  • List schemes when safe
  • Ask for scheme if ambiguous
  • Run the approved build or test command
  • Parse errors by root cause
  • Propose a scoped fix plan
  • Verify with the smallest command

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.