iso-init-repo

iso-init-repo

Set up GitHub repo governance. Run from inside the target repo.

All templates live in templates/ next to this file.

Pre-flight

Run these checks before any step.

git

command -v git &>/dev/null \
  || { echo "✗ git not found. Install Xcode CLI tools: xcode-select --install"; exit 1; }

gh (GitHub CLI)

if ! command -v gh &>/dev/null; then
  echo "⚠ gh not found — installing..."
  brew install gh
  command -v gh &>/dev/null \
    || { echo "✗ gh install failed. Run manually: brew install gh"; exit 1; }
  echo "✓ gh installed"
fi

gh authentication

Authentication is interactive — cannot be automated. If not authenticated, stop and run the login command manually.

if ! gh auth status &>/dev/null; then
  echo "⚠ gh not authenticated."
  echo "  Run: gh auth login"
  echo "  Then re-run /iso-init-repo"
  exit 1
fi

Remote detection

git remote get-url origin 2>/dev/null || echo "no remote"

All checks pass → proceed to Step 1.

Idempotency

Every step probes its own postcondition first and skips when already met. Re-running on a governed repo is safe and expected — it is the documented path after upgrading a plan, and the only way a repo set up by an older version of this skill gets repaired.

Report each skip out loud (⏭️ dev already default) rather than silently doing nothing. A step that is quiet about skipping is indistinguishable from a step that is broken.

Step 1 — GitHub repo

No remote → create

Ask user for repo name (default: current directory name) and visibility (private/public).

gh repo create <name> --private --source=. --remote=origin --push

Remote exists → verify

gh repo view --json nameWithOwner,visibility -q '"⏭️ repo exists: \(.nameWithOwner) (\(.visibility))"'

Confirm accessible, then continue.

Step 2 — Branch structure

Target: dev (default, daily work) ← test (staging) ← prod (release)

Record the branch the repository started on before anything moves — Step 2's second half needs it, and by then HEAD has moved: