メニュー
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 に表示されている付属ファイルをお読みください。
SOC 職業分類に基づく
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/aberson/skill-mesh --skill repo-initコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
SKILL.md を表示中
Read exact lifecycle markers from this disposable plugin's shared reference. Use when a request contains the unique trigger {{TRIGGER_ALPHA}}.
Read exact lifecycle markers from this disposable plugin's shared reference and helper asset. Use when a request contains the unique trigger {{TRIGGER_BETA}}.
Auto-generate an evaluation framework (evals.json + test_scenarios.json) for any skill by reading its SKILL.md, then output a ready-to-paste self-improvement loop prompt. Use as "/skill-eval-setup <skill-name-or-path>".
| 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