菜单
Default custom rules for creating new GitHub repos on this machine with `ghwrc`. Use whenever the user asks to create a new GitHub repository, initialize a new repo in the shared bare-clone/worktree layout, or create the remote and local worktree together.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user wants to run a long or resource-heavy task on another computer so their local machine stays free, the work continues if they close their laptop or lose connection, and the result returns as a reviewable branch in their project. Use this skill also when no offload target exists yet and the user needs help setting one up.
Use for dispatching a command from the current git repo to a remote machine in order to offload work for execution.
Clone GitHub repos on this machine with ghwc: canonical owner/repo casing, shared bare clone, branch-named sibling worktrees under ~/Projects.
Use this skill for any task involving the ambit CLI: creating or destroying private networks, deploying apps to a private network, checking network or router health, listing routers, diagnosing connectivity problems, managing app secrets, or streaming app logs. Trigger phrases include "create a network", "set up ambit", "deploy with ambit", "ambit create", "ambit deploy", "ambit doctor", "check router status", "destroy a network", "managing app secrets", "streaming app logs", and similar.
Use when inspecting state, output, completion, or worktree activity for Codex goal runs launched by Boondoggle.
Use when launching a persistent Codex goal run with `boondoggle` from a prompt on stdin.
| name | ghwrc-repos |
| description | Default custom rules for creating new GitHub repos on this machine with `ghwrc`. Use whenever the user asks to create a new GitHub repository, initialize a new repo in the shared bare-clone/worktree layout, or create the remote and local worktree together. |
You are the agent supervising this machine. When the user asks to create a GitHub repo, create the remote and local worktree from here, then report the resulting repo URL and local path.
ghwrc creates the GitHub repository, then creates or reuses the local shared bare clone and adds a worktree under ~/Projects by default.
For OWNER/REPO, the normal layout is:
~/Projects/gh/OWNER/REPO/
├── .bare/
└── main/
Always pass exactly one visibility flag:
ghwrc --private OWNER/NEW-REPO main
ghwrc --public --add-readme OWNER/NEW-REPO main
ghwrc --internal OWNER/NEW-REPO main
Common creation options:
ghwrc --private --description "Short description" OWNER/NEW-REPO main
ghwrc --public --add-readme --license mit OWNER/NEW-REPO main
ghwrc --private --template OWNER/TEMPLATE OWNER/NEW-REPO main
ghwrc --private OWNER/NEW-REPO feature-x -b feature-x
If the new repo has no initial content and no explicit branch mode, ghwrc creates an orphan worktree so there is somewhere to make the first commit.
GHWRC_ROOT overrides the root; it defaults to ~/Projects.--repo-path PATH overrides the gh/OWNER/REPO path under the root.--bare-dir DIR overrides the shared bare repo path.--base BRANCH selects the branch used as the starting point when the repo has initial content.-b, -B, --detach, and --orphan are mutually exclusive.--description, --homepage, --team, --template, --add-readme, --gitignore, and --license are forwarded to gh repo create.git worktree add flags such as --filter, --depth, --jobs, --track, and --reason are forwarded. Run ghwrc --help for the exact list.The repo parser accepts forms such as OWNER/REPO, github.com/OWNER/REPO, git@github.com:OWNER/REPO.git, and https://github.com/OWNER/REPO.git. GitHub repos land under gh/OWNER/REPO; less specific names fall back to git/REPO.