GIT-001 critical clone-and-run

Clone and run immediately

Repository can be cloned, built, and run without external system setup

Question to ask

"Can a new hire be running locally in under 10 minutes?"

Verification guide

Severity: Critical

Verification steps:

  1. Get the repo URL from project config — read projects/<project>.yaml and use the repo field:

    # Clone using the repo field from project config (e.g., acme-corp/acme-api)
    CLONE_DIR="/tmp/audit-clone-test-$(date +%s)"
    git clone [email protected]:<owner>/<repo>.git "$CLONE_DIR"
    # If SSH fails, fall back to HTTPS:
    # git clone https://github.com/<owner>/<repo>.git "$CLONE_DIR"
    cd "$CLONE_DIR"
    

    Do NOT ask the user for the repo URL — it's already in the project config.

  2. Spawn subagent to work in the cloned directory:

    • Read README for setup instructions
    • Install dependencies (npm install, pip install, etc.)
    • Build the app (npm run build, etc.) - dev mode can hide issues
    • Run the app in dev mode
    • Report any errors encountered
  3. Pass criteria:

    • Dependencies install without errors
    • App builds successfully
    • App runs in dev mode without critical errors
    • No manual intervention required (no "go get X API key first")
  4. Evidence to capture:

    • Time from clone to running
    • Build output (success/warnings/errors)
    • Any warnings (acceptable) vs errors (failure)
    • What commands were needed

If fails: Document exactly where it broke and what was missing.


Section

01. Git Repo Setup & Security

Infrastructure & Setup