
Compare Cache Runs
When your CI cache hit rates tank after a merge, this skill helps you figure out why. It compares two tuist cache runs (by ID, dashboard URL, or branch name), calculates hit rate deltas, and traces which modules triggered the invalidation cascade. The real value is in the root cause analysis: it distinguishes between targets with direct source changes versus the dozen downstream modules that got invalidated just because their dependency hash changed. You get a breakdown showing duration regression, cache metrics, and specific recommendations like splitting fat modules or warming caches after rebasing. Saves you from manually diffing JSON output and guessing which changed file nuked your cache warming strategy.
- skills.sh installs
- 284
- GitHub stars
- 35
- last updated
- Aug 21, 2026
Install
$ npx -y skills add tuist/agent-skills --skill compare-cache-runs --agent claude-codeInstalls into .claude/skills of the current project.
Files
Compare Cache Runs
Quick Start
You'll typically receive two cache run identifiers. Follow these steps:
- Run
tuist cache-run list --jsonto find cache runs on each branch. - Run
tuist cache-run show <id> --jsonfor both base and head cache runs. - Compare duration, status, and cache hit rates.
- Summarize cache changes with root cause analysis.
Step 1: Resolve Cache Runs
If base/head are cache run IDs or dashboard URLs
Fetch each directly:
tuist cache-run show <base-id> --json
tuist cache-run show <head-id> --json
If base/head are branch names
List recent cache runs on each branch:
tuist cache-run list --git-branch <base-branch> --json --page-size 1
tuist cache-run list --git-branch <head-branch> --json --page-size 1
Then fetch full details with tuist cache-run show <id> --json.
Defaults
- If no base is provided, use the project's default branch (usually
main). - If no head is provided, detect the current git branch.
Step 2: Compare Top-Level Metrics
After fetching both cache runs, compare:
Sponsors
Details
- Repository
- github.com/tuist/agent-skills
- Categories
- Git & Pull Requests, AI & Agent Building
- First seen
- Jun 3, 2026