Skip to main content
skill CX Codex

compare-test-runs — Claude Code skill: overview & setup

compare-test-runs compares two Tuist test executions to spot fresh failures, newly flaky suites, and execution duration spikes.

no license 265 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-test-runs -a claude-code
Open on GitHub

What compare-test-runs does

This skill evaluates test runs side by side. It accepts run identifiers, web dashboard URLs, or git branch references. When omitted, it defaults to checking your active branch against the default branch, which is typically main.

The logic relies entirely on Tuist CLI commands. The agent queries run data with tuist test show and itemizes individual cases via tuist test case run list using JSON output. It maps cases across modules, sorting them into clear categories: newly broken tests, resolved cases, newly flaky behavior, and runtime spikes exceeding 50%.

Without the tuist binary available in your shell environment, the skill cannot fetch test telemetry. Its finished summary highlights failing assertions alongside precise source paths and line numbers.

What it helps with

  • detect newly broken tests between base and feature branches
  • catch flaky test cases before merging pull requests
  • isolate test duration regressions across modules
  • extract failure lines and stack traces from test reports

Example prompts for the agent

  • Compare test runs between main and my current branch using Tuist
  • Inspect test run IDs run-123 and run-456 to show what broke
  • Check the latest test results for branch feature-cache and list newly flaky tests

How to install compare-test-runs

1Skills CLI (Vercel)

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

2Manually: put the files in place

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

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

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

Questions about compare-test-runs

How to install compare-test-runs in Claude Code?

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

What does the compare-test-runs skill do?

It queries Tuist test metadata to contrast two test runs, classifying failures, flaky tests, and execution time changes.

What prerequisite does this skill require?

It requires the tuist CLI installed and accessible, as the assistant invokes tuist test commands under the hood.

Similar skills

All skills for Testing and QA →

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-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