init-repolisted

# Init Repo Goal: Go from "no repository" to "an empty repository with a clean root commit, checked out locally on a `bootstrap` branch, ready for the first real work". The design intent: `main` starts as a single empty commit and stays clean. Everything that makes the repository useful — README, license, tooling — arrives later via pull requests from the `bootstrap` branch. This skill only prepares that starting line; it never writes project files itself. ## Why an empty init commit A root commit with no files gives every later change — including the very first README — a parent to diff against, keeps `git rebase -i --root` and `git bisect` well-behaved, and means the actual scaffolding can go through a reviewable PR instead of being baked into the root. ## Workflow ### 0) Preconditions `gh auth status` and `ghq root` must both succeed. Surface errors and stop on failure. ### 1) Gather the essentials From the user (or the conversation), determine: - **Repository name** — required. - **Visibility** — `--public` or `--private`. If not stated, ask; never guess. Publishing a repository is outward-facing. - **Owner** — default to the authenticated user, resolved concretely with `gh api user --jq .login` (a machine may hold several `gh` accounts). Only ask when an organization is plausibly intended. - **Description** — optional; include only if the user provides one. Confirm the combination (`owner/name`, visibility) with the user before creating. This is the one