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.
89
88%
Does it follow best practices?
Impact
85%
3.14xAverage score across 3 eval scenarios
Passed
No known issues
CI/CD build script Jahro disable configuration
Uses JAHRO_DISABLE define
0%
100%
Correct Unity API for defines
100%
100%
Platform-specific target group
100%
100%
Semicolon-separated defines
100%
100%
Build log validation step
30%
100%
Exact log message
0%
100%
JAHRO_DISABLE is highest priority
0%
70%
Command-line alternative documented
0%
0%
Near-zero overhead note
0%
0%
No API key exposure
0%
0%
Troubleshooting guidance
33%
100%
Auto-disable and three-tier priority configuration advice
Auto-disable as primary recommendation
0%
100%
Auto-disable location
0%
100%
JAHRO_DISABLE for CI/CD
0%
100%
Scripting Define Symbols path
30%
20%
Semicolon-separated defines
0%
100%
Manual toggle stays on
0%
62%
Priority order explained
0%
100%
Debug.isDebugBuild mechanism
0%
75%
Build log validation
0%
100%
jahro-settings.asset in VCS
0%
100%
Release vs Development build distinction
50%
100%
Runtime validation code and production readiness checklist
Preprocessor directive used
50%
100%
Jahro.Enabled runtime check
10%
100%
Warning when unexpectedly enabled
62%
100%
Build log message check
0%
100%
Auto-disable in Release Builds
0%
100%
Release not Development build
100%
100%
Console hotkey test
87%
100%
Jahro.Enabled returns false check
0%
100%
API key not exposed
62%
100%
jahro-settings.asset in VCS
25%
100%
Development build confirmation
0%
33%
No large proprietary downloads
100%
100%
300b45d
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.