GIT-002 critical clone-and-run
Sandbox env vars ready
Sandbox/development environment variables provided in .env.example or .env
Question to ask
"Missing one key — does everything break with no explanation?"
Verification guide
Severity: Critical
Check automatically:
- Look for files:
.env.example,.env.sample,.env.development,env.example,.env - If
.envis committed, verify it contains only sandbox keys (no real secrets) - Warn if
.env.localis committed - this should never be in repo (contains personal overrides) - Verify example file contains actual values (not just empty
API_KEY=) - Compare against what the app actually requires (check code for
process.env.Xor equivalent)
Pass criteria:
- Env example file exists (or
.envwith sandbox values) - Contains all required variables with working sandbox/example values
- A developer can copy to
.env(or use committed.env) and run without edits - No
.env.localcommitted
Fail criteria:
- No env example file at all
.env.localis committed.envcontains real secrets (not sandbox)- Required variables missing from example