메뉴
Use when a local project directory has no GitHub repo and needs to be published — initializing git, creating the remote repo, adding a README, and converting a plan document into GitHub issues.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/aberson/skill-mesh --skill repo-init명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | repo-init |
| description | Use when a local project directory has no GitHub repo and needs to be published — initializing git, creating the remote repo, adding a README, and converting a plan document into GitHub issues. |
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.
Confirm these inputs before any git or gh command runs:
gh user)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.
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.
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>"
gh repo create <repo-name> --private --source=. --remote=origin --push
# or --public if requested
Generate README.md from the plan. A good README includes:
Do not duplicate the full plan — summarize and surface what a new contributor needs to get started.
Commit and push:
git add README.md
git commit -m "Add README
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>"
git push
Read the build order section of the plan. Create one issue per step using gh issue create.
The plan typically labels build steps under a "Build Order" or "Steps" heading; if no such section exists, ask the user how to slice the work before any issues are filed.
Issue body structure for each:
## Build step N of M### Files — list of files to produce### What to build — concrete description drawn from the plan### Quality gates — test/lint/typecheck commands### Notes — key constraints or gotchas from the planCreate issues one at a time with separate gh issue create calls (not batched in a single shell command) to avoid quoting failures.
gh issue create --title "Step N: <title>" --body "<body>"
git or gh command runs.plan.md (or equivalent) before writing the README or creating issues; both are derived from it.gh issue create once per issue; never stack multiple heredocs in one shell command.Co-Authored-By: Claude trailer in the scaffold commit and the README commit.git init when .git already exists in the project directory.gh CLI authenticated with repo scope; org repos under restricted-policy may still reject the gh repo create call.plan.md as the single source for README and issues; multi-plan or wiki-style sources are out of scope.Batching issue creates in one shell command
gh issue create call per issue, separate Bash tool callsWriting the README before reading the plan
Skipping the inputs check