Debug Generated Project

This one automates the full triage cycle when users hit issues with Tuist project generation. It reproduces the problem locally, tests against both the latest release and main branch built from source, then figures out if you're looking at a bug, a misconfiguration, or something that needs team eyes. The runtime verification step is solid: it actually boots a simulator and launches the app with console output piped, so you catch crashes that only show up after generation and build succeed. If it's a bug, it walks you through opening a PR with a minimal reproduction zipped up. If it's user error, it explains the fix with corrected manifest snippets. Saves you from the clone, build, reproduce loop every time someone reports a generation failure.

skills.sh installs: 533
GitHub stars: 35
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add tuist/agent-skills --skill debug-generated-project --agent claude-code

Installs into .claude/skills of the current project.

Files

Debug Tuist Project Issue

Quick Start

Ask the user to describe the issue and the project setup (targets, dependencies, configurations, platform).
Confirm the issue exists with the latest release by running mise exec tuist@latest -- tuist generate against a reproduction project.
If confirmed, clone the Tuist repository and build from source to test against main.
Triage: fix the bug and open a PR, advise on misconfiguration, or recommend the user files an issue with a reproduction.

Step 1: Gather Context

Ask the user for:

What command they ran (e.g. tuist generate)
The error message or unexpected behavior
When the issue happens: generation time, compile time, or runtime (app launch or later)
Their project structure: targets, platforms, dependencies (SwiftPM, XCFrameworks, local packages)
Their Project.swift and Tuist.swift content (or relevant excerpts)
Their Tuist version (tuist version)

The answer to "when" determines the verification strategy:

SKILL.md on GitHub