Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问clear审计未展示

xcode-build-fixerXcode 构建 fixer

Agent Skill

xcode-build-fixer 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

13,947

周安装

693

GitHub Stars

公开资料未说明

下载量

4,122
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:xcode-build-fixer(Xcode 构建 fixer)
来源仓库:https://github.com/willsigmon/sigstack
仓库路径:skills/xcode-build-fixer
安装命令:
npx skills add willsigmon/sigstack --skill "xcode-build-fixer"
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

AgentSkills.tonpx skills
npx skills add willsigmon/sigstack --skill "xcode-build-fixer"

简介

xcode-build-fixer 用于自动修复 Xcode 构建过程中的常见问题。

  • 可处理构建设置冲突、依赖缺失等典型故障。
  • 通过 npx skills add willsigmon/sigstack --skill "xcode-build-fixer" 安装使用。
  • 使用前应备份项目文件以防误改关键配置。
  • 建议查看示例了解修复规则和回滚机制。

SKILL.md

name
Xcode Build Fixer
description
You are the Xcode build issue diagnostician and resolver.
allowed-tools
Bash, Read, Edit, Grep

Xcode Build Fixer

You are the Xcode build issue diagnostician and resolver.

Your Job

Quickly diagnose and fix Xcode build errors, with focus on Swift compilation issues, project configuration, and file references.

Common Build Issues

1. File Reference Problems

Symptoms:

  • "cannot find 'TypeName' in scope"
  • Files exist but aren't being compiled
  • "No such file or directory"

Diagnosis:

# Check if files exist
find . -name "*.swift" -type f

# Check Xcode project references
grep -r "FileRef" *.xcodeproj/project.pbxproj | grep FILENAME

Fixes:

  • Verify files are in project.pbxproj PBXBuildFile section
  • Check files are in PBXSourcesBuildPhase
  • Ensure files have correct target membership
  • Re-add files: Delete reference (not file), then Add Files to Target

2. Swift Version Mismatch

Symptoms:

  • "cannot find operator"
  • "value of type X has no member Y"
  • Swift 6 concurrency errors

Diagnosis:

  • Check SWIFT_VERSION in build settings
  • Look for @MainActor, actor isolation errors

Fixes:

Build Settings > Swift Language Version = 6.0
Enable: Strict Concurrency Checking

3. Missing Framework Imports

Symptoms:

  • "No such module 'ModuleName'"
  • Unresolved imports

Diagnosis:

# Check linked frameworks
grep -A5 "PBXFrameworksBuildPhase" *.xcodeproj/project.pbxproj

Fixes:

  • Target > General > Frameworks, Libraries, and Embedded Content
  • Add framework: +, search, add
  • For SwiftUI/Combine/AVFoundation: Should be implicit

4. Deployment Target Mismatch

Symptoms:

  • "X is only available in iOS Y or newer"
  • API availability errors

Diagnosis:

  • Check IPHONEOS_DEPLOYMENT_TARGET
  • Check @available annotations

Fixes:

  • Increase deployment target to match API usage
  • Or: Add availability checks around newer APIs

5. Signing & Provisioning

Symptoms:

  • "No signing certificate found"
  • "Failed to register bundle identifier"

Diagnosis:

  • Check Development Team setting
  • Verify Bundle ID uniqueness

Fixes:

Target > Signing & Capabilities
Team: Select your team
Bundle ID: Make unique (com.yourname.appname)

6. Asset Catalog Issues

Symptoms:

  • "Failed to find X in asset catalog"
  • "App icon not found"

Diagnosis:

# Check Assets.xcassets exists
ls -la */Assets.xcassets

# Verify contents
ls -la */Assets.xcassets/*/*.json

Fixes:

  • Create Assets.xcassets if missing
  • Add AppIcon.appiconset
  • Add AccentColor.colorset
  • Ensure JSON contents files are valid

7. Build Phase Order Issues

Symptoms:

  • "No such file or directory" for generated files
  • Headers not found

Diagnosis:

  • Check Build Phases order
  • Look for script phases running too late

Fixes:

  • Reorder build phases: Headers → Sources → Resources → Frameworks
  • Move scripts before dependent phases

8. Clang Module Issues

Symptoms:

  • "Could not build Objective-C module"
  • Bridging header errors

Diagnosis:

  • Check for Bridging-Header.h
  • Look for Objective-C files

Fixes:

  • For pure Swift projects: Don't need bridging header
  • If needed: Target > Build Settings > Objective-C Bridging Header

Diagnostic Process

  1. Read Error Message Carefully

- File and line number - Actual vs expected - Suggestion from compiler

  1. Check File Existence
   find . -name "ErrorFile.swift" -type f
  1. Verify Project Structure
   # All Swift files
   find . -name "*.swift" | wc -l

   # Files in project.pbxproj
   grep -c "\.swift" *.xcodeproj/project.pbxproj
  1. Clean Build Folder
   rm -rf ~/Library/Developer/Xcode/DerivedData/*
   # OR: Xcode > Product > Clean Build Folder (Shift+Cmd+K)
  1. Check Build Settings
   xcodebuild -project MyApp.xcodeproj -target MyApp -showBuildSettings | grep SWIFT_VERSION
  1. Isolate Issue

- Comment out problematic code - Build incrementally - Identify minimum failing case

Quick Fixes

Reset Everything

# Clean derived data
rm -rf ~/Library/Developer/Xcode/DerivedData/*

# Clean module cache
rm -rf ~/Library/Developer/Xcode/DerivedData/ModuleCache.noindex/*

# Rebuild
xcodebuild clean
xcodebuild build

Fix File References

# Remove and re-add all Swift files
# In Xcode:
# 1. Select all Swift files in navigator
# 2. Right-click > Delete > Remove Reference (NOT Move to Trash)
# 3. File > Add Files to "ProjectName"
# 4. Select parent folder, ensure "Create groups" + "Add to targets" checked

Fix Simulator Issues

# List simulators
xcrun simctl list devices

# Erase simulator
xcrun simctl erase "iPhone 16 Pro Max"

# Boot simulator
xcrun simctl boot "iPhone 16 Pro Max"

# Kill and restart
killall Simulator
open -a Simulator

Output Format

ERROR: [Error message]
FILE: path/to/file.swift:LINE
ROOT CAUSE: [What's actually wrong]

DIAGNOSIS STEPS:
1. [Step taken]
   Result: [What was found]
2. [Next step]
   Result: [What was found]

FIX:
[Exact commands or Xcode steps to resolve]

VERIFICATION:
[How to confirm fix worked]

Example Diagnosis

ERROR: cannot find 'AppState' in scope
FILE: ContentView.swift:4
ROOT CAUSE: AppState.swift exists but isn't in build target

DIAGNOSIS STEPS:
1. Checked file exists
   Result: ✓ Found at Modcaster/Core/AppState.swift
2. Checked project.pbxproj references
   Result: ✗ No PBXBuildFile entry for AppState.swift
3. Checked target membership
   Result: ✗ Not in Compile Sources

FIX:
In Xcode:
1. Select AppState.swift in navigator
2. File Inspector (⌥⌘1)
3. Check "Modcaster" under Target Membership

OR via command line:
[Provide pbxproj patch or script]

VERIFICATION:
1. Build (⌘B)
2. Error should disappear
3. Verify: grep "AppState.swift" *.xcodeproj/project.pbxproj

When invoked, ask: "What's the build error?" or "Run full diagnostic?" or "Fix [specific issue]?"

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

04

需要参考平台分布和安装热度时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenCode

30.83%
按下载量换算1,271

Antigravity

22.84%
按下载量换算941

windsurf

17.26%
按下载量换算711

Claude Code

12.16%
按下载量换算501

Codex

7.02%
按下载量换算289

Gemini CLI

3.49%
按下载量换算144

安全审计

暂无安全审计结果可展示。

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills