Skip to main content
skill CX Codex

compare-gradle-builds — Claude Code skill: what it does and setup

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.

no license 239 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-gradle-builds -a claude-code
Open on GitHub

What compare-gradle-builds does

This skill evaluates two Gradle runs to identify why a build slowed down. It accepts run identifiers, web dashboard URLs, or branch names. When you omit the baseline, it selects the repository default branch, picking the current branch via git rev-parse --abbrev-ref HEAD as the target.

The analysis checks high-level figures and granular tasks. It flags execution if duration climbs over 10%, calculates local versus remote cache hit rates, and surfaces tasks shifting from cache hits to executed states. It also notes differences across Java or Gradle environments.

Tuist MCP tools must be configured in your environment beforehand; without tools like get_gradle_build, the agent cannot retrieve any run data.

What it helps with

  • spot Gradle build execution time regressions above 10%
  • detect tasks losing remote or local cache hits
  • compare task failure states between git branches
  • check Java and Gradle version differences across builds

Example prompts for the agent

  • Compare the latest build on this branch against main
  • Investigate cache hit differences between build abc123 and def456
  • Check why duration increased between these two dashboard run URLs

How to install compare-gradle-builds

1Skills CLI (Vercel)

npx skills add tuist/agent-skills --skill compare-gradle-builds -a claude-code

2Manually: put the files in place

~/.claude/skills/compare-gradle-builds/SKILL.md

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

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

Questions about compare-gradle-builds

How to install compare-gradle-builds in Claude Code?

Run npx skills add tuist/agent-skills --skill compare-gradle-builds -a claude-code in your terminal.

What does compare-gradle-builds do?

It contrasts two Gradle executions, reports on duration, cache hit variations, and task outcomes, and suggests corrective steps.

What are the prerequisites for this skill?

Your agent environment must have Tuist MCP tools enabled to run get_gradle_build and fetch build metrics.

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-cache-runs 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. CX Codex +1 291installs 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

Project sponsors

Companies that keep this analytics open