xcode-build-orchestrator 是做什么的？
编排 Xcode 构建优化流程：先基准测试，再运行专项分析技能，对发现的问题进行优先级排序，请求明确批准，将批准的修复委托给 xcode-build-fixer，最后在变更后重新基准测试。当开发者希望获得端到端的构建优化工作流、要求加速 Xcode 构建、需要进行全面构建审计，或需要涵盖编译、项目设置和包的推荐优先优化流程时使用。
编排 Xcode 构建优化流程：先基准测试，再运行专项分析技能，对发现的问题进行优先级排序，请求明确批准，将批准的修复委托给 xcode-build-fixer，最后在变更后重新基准测试。
avdlee/xcode-build-orchestrator 是一个 AI 代理技能，用于编排端到端的 Xcode 构建优化工作流。它首先运行基准测试以建立性能基线，然后调用一系列专门的 Xcode 构建分析技能（涵盖编译、项目设置和包管理），对发现的问题进行优先级排序。在应用任何修复之前，它会向开发者请求明确的批准，然后使用 xcode-build-fixer 技能自动部署批准的修复。完成更改后，它会再次运行基准测试以量化改进效果。该技能支持 Claude Code、Cursor 和 Codex 等 AI 代理平台，适用于希望加速 Xcode 构建、进行全面构建审计或实施推荐优先的优化流程的开发者。
npx skills add https://github.com/avdlee/xcode-build-optimization-agent-skill/tree/main/skills/xcode-build-orchestratorInstalled? Explore more 研究与数据分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
编排 Xcode 构建优化流程：先基准测试，再运行专项分析技能，对发现的问题进行优先级排序，请求明确批准，将批准的修复委托给 xcode-build-fixer，最后在变更后重新基准测试。当开发者希望获得端到端的构建优化工作流、要求加速 Xcode 构建、需要进行全面构建审计，或需要涵盖编译、项目设置和包的推荐优先优化流程时使用。
This repo contains 5 individual skills — each has its own dedicated page.
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build plugin overhead, duplicate module builds from configuration drift, circular dependencies between modules, oversized modules needing splitting, or modularization best practices.
Benchmark Xcode clean and incremental builds with repeatable inputs, timing summaries, and timestamped `.build-benchmark/` artifacts. Use when a developer wants a baseline, wants to compare before and after changes, asks to measure build performance, mentions build times, build duration, how long builds take, or wants to know if builds got faster or slower.
Apply approved Xcode build optimization changes following best practices, then re-benchmark to verify improvement. Use when a developer has an approved optimization plan from xcode-build-orchestrator, wants to apply specific build fixes, needs help implementing build setting changes, script phase guards, source-level compilation fixes, or SPM restructuring that was recommended by an analysis skill.
Analyze Swift and mixed-language compile hotspots using build timing summaries and Swift frontend diagnostics, then produce a recommend-first source-level optimization plan. Use when a developer reports slow compilation, type-checking warnings, expensive clean-build compile phases, long CompileSwiftSources tasks, warn-long-function-bodies output, or wants to speed up Swift type checking.
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.
USPTO patent and trademark data workflow for official record lookup, PatentSearch queries, TSDR checks, assignment data, and reproducible IP research logs.
Structured scholarly-work evaluation for papers, proposals, literature reviews, methods sections, evidence quality, citation support, and research-writing feedback.
Systematic literature-review workflow for academic, biomedical, technical, and scientific topics, including search planning, source screening, synthesis, citation checks, and evidence logging.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
Agent skill repository discovered by 10x-chat research.
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.