compare-builds — Claude Code skill: what it does, how to install
compare-builds analyzes two Xcode runs to spot build duration regressions, cache hit rate drops, and new compile issues via Tuist.
no license 317 installs ★ 35 updated 2026-03-27
npx skills add tuist/agent-skills --skill compare-builds -a claude-codeWhat compare-builds does
This skill compares two Xcode runs using build identifiers, web dashboard URLs, or git branch names. When given a single identifier, it uses the repository default branch as the baseline and identifies the current branch with git rev-parse.
The skill fetches build records with tuist build show --json, then queries targets, issues, and cache tasks. It computes the total cache hit rate and tracks target runtimes. An increase in duration greater than 10% is marked as a regression.
Execution requires a functional tuist CLI in your environment. Comparing an incremental run against a clean build skews performance numbers. The output flags mismatched build categories so you avoid misleading conclusions.
What it helps with
- detect Xcode build slowdowns across different branches
- isolate target-level drops in Tuist cache hit rates
- catch newly introduced warnings or compiler errors
- verify whether dependency changes broke cache validity
Example prompts for the agent
- Compare the build for feature-checkout against main
- Inspect build runs bld_abc123 and bld_def456 to see why build time increased
- Analyze cache misses between the latest run and the default branch
How to install compare-builds
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-builds -a claude-code2Manually: put the files in place
~/.claude/skills/compare-builds/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/compare-builds/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-builds -a codex2Manually: put the files in place
.agents/skills/compare-builds/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-builds -a cursor2Manually: put the files in place
.cursor/skills/compare-builds/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tuist/agent-skills skills/compare-builds2Manually: put the files in place
.github/skills/compare-builds/SKILL.md1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-builds -a gemini-cli2Platform CLI
gemini skills install https://github.com/tuist/agent-skills --path skills/compare-buildsManually: put the files in place
.devin/skills/compare-builds/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-builds -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about compare-builds
How do I install compare-builds in Claude Code?
Run npx skills add tuist/agent-skills --skill compare-builds -a claude-code in your terminal.
What does the compare-builds skill do?
It queries Tuist build records via JSON commands, checks target durations and cache statistics, and presents a verdict explaining any build slowdowns.
What prerequisites are required for accurate comparisons?
You need the tuist CLI installed. Runs should share the same scheme, configuration, and category, because comparing clean runs against incremental ones produces inaccurate conclusions.