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
npx skills add tuist/agent-skills --skill compare-gradle-builds -a claude-codeWhat 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-code2Manually: put the files in place
~/.claude/skills/compare-gradle-builds/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/compare-gradle-builds/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-gradle-builds -a codex2Manually: put the files in place
.agents/skills/compare-gradle-builds/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-gradle-builds -a cursor2Manually: put the files in place
.cursor/skills/compare-gradle-builds/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tuist/agent-skills skills/compare-gradle-builds2Manually: put the files in place
.github/skills/compare-gradle-builds/SKILL.md1Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-gradle-builds -a gemini-cli2Platform CLI
gemini skills install https://github.com/tuist/agent-skills --path skills/compare-gradle-buildsManually: put the files in place
.devin/skills/compare-gradle-builds/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tuist/agent-skills --skill compare-gradle-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-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.