メニュー
Use GitHub CLI (`gh`) for all GitHub interactions. Prefer built-in `gh` commands; use `gh api` only when needed.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | github |
| description | Use GitHub CLI (`gh`) for all GitHub interactions. Prefer built-in `gh` commands; use `gh api` only when needed. |
| allowed-tools | Bash |
Use gh (via Bash) for all GitHub operations.
Rules:
gh issue, gh pr, gh repo, gh search, gh release, etc.).gh api only if a built-in command cannot do the task.gh --helpgh <command> --helpgh <command> <subcommand> --help--json and parse with jq.When inside a git repo, gh usually infers the target repo. Otherwise use -R owner/repo.
# Issues (read)
gh issue list --state open -R owner/repo
gh issue view 123 --comments -R owner/repo
# Pull requests (read)
gh pr list --state open -R owner/repo
gh pr view 456 --comments -R owner/repo
gh pr diff 456 -R owner/repo
gh pr checks 456 -R owner/repo
# Repository/search
gh repo view owner/repo
gh search issues "memory leak" --repo owner/repo
gh search prs "author:octocat" --repo owner/repo
# JSON output
gh pr list -R owner/repo --json number,title,author --jq '.[] | {number,title,author:.author.login}'
# Fallback: API only when built-ins are insufficient (read endpoints)
gh api repos/owner/repo/issues
gh api --paginate repos/owner/repo/pulls
gh auth status
Write plans intended for a cheaper or less capable implementation model. Use when the user asks for a plan suitable for another LLM, junior engineer, intern, cheaper model, coding agent, or implementation delegate.
Use when the user asks for ideas, brainstorming, discussion, exploration, possibilities, pros and cons, tradeoffs, or to "think through" something.
Use this skill when asked to plan something, or plan and implement. Do not use when asked to implement a plan.
Use when initializing Rust projects or modifying Cargo.toml, Cargo.lock, cargo config, or other cargo-related files. Prefer this skill for dependency changes, features, package metadata, workspaces, and cargo commands. Do not load it for editing Rust source code generally.
Split an existing commit or PR into smaller reviewable pieces through a one-hunk patch queue. Use when extracting part of a commit, splitting a commit into multiple commits, or splitting PR changes from one or more source commits without starting from direct source edits.
Checkpoint, inspect, and return through session tree branches. Use when exploring uncertain approaches, investigating code, or when the user asks for a forked agent.