Add Enchanted, Wikipedia iOS, and Kickstarter iOS to the community
results table with links to their upstream PRs.
Replace vague COMPILATION_CACHING language ("impact uncertain",
"trust documented benefit") with data-backed framing across all
skill docs: "Measured 5-14% faster clean builds across tested
projects (87 to 1,991 Swift files). Benefit compounds during
branch switching and pulling changes."
Standard clean builds show cache-population overhead without the
corresponding cache-hit benefit, making COMPILATION_CACHING appear
to regress performance. The new "cached clean" phase measures clean
builds with a warm compilation cache by deleting DerivedData (not
the system compilation cache) between runs. This captures the
realistic developer workflow: branch switching, pulling changes,
and Clean Build Folder.
Changes:
- benchmark_builds.py: auto-detect COMPILATION_CACHING and run
cached clean builds using a controlled DerivedData path
- Schema bumped to 1.2.0 with optional cached_clean runs/summary
- Report generator shows Cached Clean column when data is present
- All skill docs and references updated to use the cached clean
metric as the primary comparison for COMPILATION_CACHING impact
User feedback showed the skills were over-indexing on cumulative task time
(which Xcode parallelizes) and presenting it as build-time savings. This led
to many source-level fixes that reduced compiler workload without actually
reducing how long the developer waits.
Key changes:
- AGENTS.md: wall-clock first principle inherited by all skills
- Orchestrator: blocking-vs-parallel heuristics, impact language templates,
wall-clock-first final report
- Report script/template: timing-table disclaimers, wait-time impact field,
plain-language verification
- Compilation analyzer: parallel workload labeling when not on critical path
- Project/SPM analyzers: wall-clock qualifier on prioritization tiers
- Fixer: wall-clock delta leads reporting, honest language when task metrics
improve but wait time does not
- Benchmark artifacts: documents wall-clock vs cumulative distinction
- Recommendation format: new wait_time_impact required field
- Updated README.md to include a quick start guide for the xcode-build-orchestrator skill and detailed installation instructions.
- Added a new script, check_spm_pins.py, to scan for branch-pinned SPM dependencies and check tag availability.
- Enhanced benchmark_builds.py to support measuring real incremental builds with a new --touch-file option.
- Expanded generate_optimization_report.py to auto-generate recommendations based on audit results.
- Revised multiple SKILL.md files to clarify usage instructions and best practices for various skills, including zero-change build analysis and worktree considerations.
- Added sections on measurement caveats related to compilation caching and first-run variance in `benchmark-artifacts.md`.
- Updated `build-optimization-sources.md` with insights from Swift forums regarding slow incremental builds due to planning Swift modules.
- Improved `benchmark_builds.py` to include a warmup clean+build cycle for better cache performance measurement.
- Expanded `generate_optimization_report.py` to include general expectations for compilation caching.
- Revised multiple SKILL.md files to clarify verification processes for local packages and version pins, and to address Swift macro rebuild impacts.
- Updated orchestration report template to note limitations of measuring `COMPILATION_CACHING` improvements.
First versioned snapshot of the full skill repository including:
- Five installable agent skills under skills/
- Shared references, schemas, and helper scripts
- Plugin and marketplace metadata for Claude Code
- GitHub workflows for release and README sync
- Compilation caching as a recommended build setting
- Four deeper Swift compiler diagnostic flags for compilation analysis
- Fixed SWIFT_COMPILATION_MODE to use singlefile (actual build setting value)
Antoine van der Lee