Tuist helps teams inspect Xcode, Gradle, and Bazel build data, test results, cache activity, previews, runner jobs, and project configuration. It also supports authorized account setup and selected test-case updates.
How to use
- 1Add it in ChatGPT
Open Tuist in ChatGPT's Plugin directory (button above), select + to add it and sign in if asked.
- 2Use it in a chat
Type @ in the composer and pick Tuist, or start your message with its name. ChatGPT may also suggest it when it fits what you ask.
Skills 12
- analyze-selective-testing
Analyzes Xcode selective testing effectiveness for a test run, showing which test targets were skipped or ran, and diagnosing regressions in test selection. Can compare two test runs to identify what changed.
- compare-builds
Compares two Xcode build runs to identify duration regressions, cache changes, and new issues. Can be invoked with build IDs, dashboard URLs, or branch names (e.g. `tuist compare-builds --base main --head feature-branch`).
- compare-bundles
Compares two app bundles to identify size changes, new or removed artifacts, and platform differences. Can be invoked with bundle IDs, dashboard URLs, or branch names.
- compare-cache-runs
Compares two `tuist cache` runs to identify cache hit rate changes and root-cause analysis of cache invalidation. Can be invoked with cache run IDs, dashboard URLs, or branch names.
- compare-generations
Compares two `tuist generate` runs to identify cache hit rate changes and root-cause analysis of cache invalidation. Can be invoked with generation IDs, dashboard URLs, or branch names.
- compare-gradle-builds
Compares two Gradle build runs to identify duration regressions, cache changes, and task outcome differences. Can be invoked with build IDs, dashboard URLs, or branch names.
- compare-test-case
Compares a single test case's behavior across two branches, analyzing pass/fail status, duration, flakiness, and failure details. Useful for investigating test regressions introduced by a feature branch.
- compare-test-runs
Compares two test runs to identify new failures, newly flaky tests, fixed tests, and duration regressions. Can be invoked with test run IDs, dashboard URLs, or branch names.
- debug-generated-project
Debugs issues users encounter with Tuist-generated projects by reproducing the scenario locally, building Tuist from source when needed, and triaging whether it is a bug, misconfiguration, or something that needs team input. Use when users report generation failures, build errors after generation, or unexpected project behavior.
- fix-flaky-tests
Fixes flaky tests by analyzing failure patterns from Tuist test insights, identifying root causes, and applying targeted corrections. Can be invoked with a specific test case URL (e.g. `https://tuist.dev/{account}/{project}/tests/test-cases/{id}`) or without arguments to discover and fix all flaky tests in the project.
- generated-projects
Guides day-to-day work in Tuist-generated Xcode workspaces, including generation, build and test commands, and buildable folders. Use when working in a Tuist-generated project or when users mention `tuist generate`, `xcodebuild test`, or generated workspaces.
- migrate
Migrates existing Xcode projects to Tuist generated workspaces with build and run validation, external dependency mapping, and migration checklists. Use when adopting Tuist for an existing app or converting a hand-edited Xcode project to generated projects.
Things to ask
- “Which tests in tuist/tuist are the flakiest, and what failure patterns do they share?”
- “Compare the two most recent build runs for tuist/tuist. What regressed in duration, cache performance, or build issues?”
- “Which targets missed the cache in tuist/tuist's latest cache run, and what should I inspect next?”