tuist-generation-doctor — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited tuist-generation-doctor (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill to determine whether a Tuist-generated workspace problem is a project configuration issue, a dependency wiring issue, or a Tuist bug.
tuist generate or tuist install.xcworkspace exists but xcodebuild failsand relevant manifest snippets.
retry with the latest Tuist release through mise.
tuist version
mise exec tuist@latest -- tuist install --path "$PROJECT_DIR"
mise exec tuist@latest -- tuist generate --no-open --path "$PROJECT_DIR"For build-stage failures:
xcodebuild build \
-workspace "$PROJECT_DIR"/*.xcworkspace \
-scheme "$SCHEME" \
-destination "platform=iOS Simulator,name=<available iPhone simulator>,OS=latest" \
-derivedDataPath "$PROJECT_DIR/DerivedData"For runtime-stage failures, launch the generated app:
xcrun simctl boot "<available simulator name or UDID>" 2>/dev/null || true
xcrun simctl install booted "$APP_PATH"
xcrun simctl launch --console-pty booted "$BUNDLE_ID"tuist install before generation.-ObjC ortargeted -force_load.
Clone Tuist only after you have a small reproduction:
TUIST_SRC="$(mktemp -d)"
git clone --depth 1 https://github.com/tuist/tuist.git "$TUIST_SRC"
cd "$TUIST_SRC"
swift build --product tuist --product ProjectDescription --replace-scm-with-registry
"$TUIST_SRC/.build/debug/tuist" generate --no-open --path "$REPRO_DIR"If the reproduction fails on Tuist main, report:
Return the failure stage, root cause, exact fix or next command, and proof from the latest generation/build/launch attempt.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.