Skip to main content
skill CX Codex

compare-cache-runs — Claude Code skill: Tuist cache analysis

compare-cache-runs is a Claude Code skill that compares two Tuist cache runs, revealing hit-rate changes, root causes, and cascade effects through dependencies.

no license 291 installs ★ 35 updated 2026-03-27

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add tuist/agent-skills --skill compare-cache-runs -a claude-code
Open on GitHub

What compare-cache-runs does

The skill takes two cache run identifiers (run ID, dashboard URL, or branch name), fetches metrics via tuist cache-run list and tuist cache-run show, and compares execution time, local and remote cache hits, and cacheable target counts.

When cache hit rate drops, the skill examines git diff to find which files changed, maps them to Tuist modules, and flags modules with direct source changes as root causes. It then calculates cascade impact: if module B depends on module A and A is invalidated, B loses cache too even though its source didn't change.

Output includes a verdict (cache improved, regressed, or stable), hit-rate delta, root cause targets, cascade breadth, and actionable recommendations like splitting large modules, using interface patterns, or pre-warming caches before merge.

What it helps with

  • compare cache hit rates between two project versions
  • identify which module broke cache for downstream targets
  • measure build-time impact of changes through cache metrics
  • distinguish expected cache misses from unexpected ones
  • get recommendations to reduce cache invalidation

Example prompts for the agent

  • Compare cache between main and my current feature branch
  • Show me why run-123 and run-456 have different hit rates
  • Analyze cache invalidation cascade from commits abc1234 to def5678

How to install compare-cache-runs

1Skills CLI (Vercel)

npx skills add tuist/agent-skills --skill compare-cache-runs -a claude-code

2Manually: put the files in place

~/.claude/skills/compare-cache-runs/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/compare-cache-runs/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about compare-cache-runs

How do I install compare-cache-runs for Claude Code?

Run npx skills add tuist/agent-skills --skill compare-cache-runs -a claude-code. The skill will be available at ~/.claude/skills/compare-cache-runs/SKILL.md and ready to use.

What does compare-cache-runs do?

It takes two Tuist cache runs, compares metrics like duration and cache hits, identifies modules with direct changes, and shows how those changes propagate through the dependency graph to affect other modules.

How does the skill determine root causes of cache invalidation?

The skill examines git diff between the two commits, maps changed files to Tuist modules, and flags modules with direct source modifications as roots. Other invalidated modules are secondary—they lost cache due to dependency changes.

Similar skills

All skills for DevOps and infrastructure →

From the same set12

The whole set →
migrating-to-tuist-generated-projects migrating-to-tuist-generated-projects is a Claude Code skill that moves an existing Xcode project into Tuist-generated files. It runs during a Tuist adoption and checks that the app builds and launches. CX Codex +1 521installs compare-builds compare-builds analyzes two Xcode runs to spot build duration regressions, cache hit rate drops, and new compile issues via Tuist. CX Codex +1 317installs analyze-selective-testing analyze-selective-testing diagnoses Tuist selective test runs in Xcode to spot skipped targets and identify cache invalidation causes. CX Codex +1 310installs compare-generations compare-generations compares two Tuist generation runs to pinpoint cache hit drops and uncover which modules caused invalidation cascades. CX Codex +1 300installs compare-bundles compare-bundles evaluates two application packages via Tuist to spot size growth and heavy files. Helpful for catching build regressions early. CX Codex +1 296installs compare-test-runs compare-test-runs compares two Tuist test executions to spot fresh failures, newly flaky suites, and execution duration spikes. CX Codex +1 265installs compare-test-case compare-test-case compares one test case across two branches: pass/fail, duration, flakiness and failure details. Useful when a feature branch seems to have broken a test. CX Codex +1 255installs compare-gradle-builds compare-gradle-builds compares two Gradle build runs to spot duration regressions, cache changes, and task failures. Works with run IDs, dashboard links, or branch names. CX Codex +1 239installs

Project sponsors

Companies that keep this analytics open