xcode-project-analyzer 是做什么的？
审计 Xcode 项目配置、构建设置、Scheme 行为和脚本阶段，通过明确的审批门控寻找构建时间改进点。当开发者需要进行项目级构建分析、排查增量构建缓慢问题、获取目标依赖关系指导、审查构建设置、分析运行脚本阶段、寻求并行化改进建议，或检查模块映射和 DEFINES_MODULE 配置时使用此技能。
审计 Xcode 项目配置、构建设置、Scheme 行为和脚本阶段，通过明确的审批门控寻找构建时间改进点。
该技能（avdlee/xcode-project-analyzer）专注于分析 Xcode 项目配置，帮助开发者诊断并优化构建性能。它能够对构建设置、Scheme 行为、运行脚本阶段以及目标依赖关系进行全面审计，识别导致增量构建缓慢、模块映射（module-map）和 DEFINES_MODULE 配置不当等问题。通过明确的审批门控机制，每次优化建议都需开发者确认后才执行，确保项目安全。技能适用于所有 Xcode 项目，尤其适合团队在大型 iOS/macOS 工程中寻找构建加速机会。主要功能包括：检查 Build Settings 中的冗余或错误配置、分析 Scheme 的测试行为、评估 Run Script Phases 的效率、提出并行化建议，以及对比 module-map 与 DEFINES_MODULE 的设置一致性。对于希望系统性提升 Xcode 构建速度的开发者而言，这是一个实用的审计工具。
npx skills add https://github.com/avdlee/xcode-build-optimization-agent-skill/tree/main/skills/xcode-project-analyzerInstalled? Explore more 研究与数据分析 skills: affaan-m/uspto-database, affaan-m/scholar-evaluation, affaan-m/literature-review · View all 6 →
审计 Xcode 项目配置、构建设置、Scheme 行为和脚本阶段，通过明确的审批门控寻找构建时间改进点。当开发者需要进行项目级构建分析、排查增量构建缓慢问题、获取目标依赖关系指导、审查构建设置、分析运行脚本阶段、寻求并行化改进建议，或检查模块映射和 DEFINES_MODULE 配置时使用此技能。
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.
Orchestrate Xcode build optimization by benchmarking first, running the specialist analysis skills, prioritizing findings, requesting explicit approval, delegating approved fixes to xcode-build-fixer, and re-benchmarking after changes. Use when a developer wants an end-to-end build optimization workflow, asks to speed up Xcode builds, wants a full build audit, or needs a recommend-first optimization pass covering compilation, project settings, and packages.
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.
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.