repo-initlisted

# Repo Init ## Overview Use this skill to take a bare local project directory all the way to a fully scaffolded GitHub repo with a README and issues. **Core principle:** Read the plan first -> git init -> push -> README -> issues, in that order. ## Steps ### 1. Confirm inputs with the user Confirm these inputs before any git or gh command runs: - Repo visibility: **public or private?** - Repo name (suggest the directory name as default) - Target account/org (default: the authenticated `gh` user) ### 2. Check prerequisites ```bash gh auth status # must show active account with repo scope ls -la <project-dir> # confirm .git does NOT exist ``` If `.git` already exists, skip step 4 (git init + first commit) and jump to step 5 (create the GitHub repo and push). Do not re-run `git init` on an existing repo. ### 3. Read the plan document Before writing any git commits or the README, read `plan.md` (or equivalent) in the project directory. This is required — the README and issues are derived from it. ### 4. Initialize git and make the first commit ```bash cd <project-dir> git init git add . git commit -m "Initial commit: <project-name> project scaffold Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>" ``` ### 5. Create the GitHub repo and push ```bash gh repo create <repo-name> --private --source=. --remote=origin --push # or --public if requested ``` ### 6. Write the README Generate `README.md` from the plan. A good README includes: - One-parag