← ClaudeAtlas

jahro-productionlisted

Configures Jahro lifecycle controls for safe production deployment including JAHRO_DISABLE, auto-disable, and build validation. Use when the user mentions production builds, release builds, disabling Jahro, shipping, CI/CD, lifecycle controls, or production safety.
Logiiiii/unity-agent-skills · ★ 2 · AI & Automation · score 75
Install: claude install-skill Logiiiii/unity-agent-skills
# Jahro Production Readiness Help users configure Jahro for safe production deployment so debugging tools never leak into release builds. ## Three-Tier Disable Mechanism Jahro evaluates these conditions at startup in priority order: ``` 1. JAHRO_DISABLE defined? → Disabled (highest priority) 2. Auto-disable ON + Release build? → Disabled 3. Enable Jahro switch → Uses switch value (lowest priority) ``` ### Tier 1: JAHRO_DISABLE Preprocessor Define **What:** Compile-time disable. When defined, Jahro exits at initialization regardless of all other settings. **How to set:** 1. Open **Edit → Project Settings → Player** 2. Under **Other Settings → Scripting Define Symbols** 3. Add `JAHRO_DISABLE` (semicolon-separated if other defines exist: `MY_DEFINE;JAHRO_DISABLE`) **When to use:** CI/CD pipelines, absolute control, platform-specific disabling (set per-platform defines). **Validation:** Build logs show "Jahro Console: Disabled in this build". ### Tier 2: Auto-disable in Release Builds **What:** Runtime check. Jahro checks `Debug.isDebugBuild` at startup. If `false` (Release build) and this setting is ON, Jahro disables itself. **How to set:** 1. Open **Tools → Jahro Settings → General Settings** 2. Enable **Auto-disable in Release Builds** **When to use:** Recommended default for most projects. Development and Debug builds keep Jahro active; Release builds automatically disable it. **Validation:** Same build log message when triggered. ### Ti