メニュー
Use when handling GitHub issues, pull requests, workflow runs, releases, or repo metadata through gh CLI.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | github |
| description | Use when handling GitHub issues, pull requests, workflow runs, releases, or repo metadata through gh CLI. |
| argument-hint | <url | owner/repo#N | issue/pr/run/release request> |
生产级 gh CLI 操作 SOP。先锁定 repo + resource + action，再执行 GitHub 平台侧操作。
git commit、git push、冲突处理、回滚skills/git/SKILL.mdgithub.com/owner/repo/issues/123、/pull/456、/commit/abc123、/actions/runs/789owner/repo#123、#123issue 123、pr 456、run 789、release v1.2.3gh 已安装：gh --versiongh auth statusgh auth refresh -s <scope>先锁定 repo，再锁定 resource，最后锁定 action。
repo 解析优先级：
owner/repo#Nowner/repoowner/reporesource 解析规则：
/issues/N 或 issue N -> issue/pull/N 或 pr N / pull request N -> pr/actions/runs/N 或 run N -> workflow_run/releases/tag/TAG 或 release TAG -> release/commit/SHA 或 commit SHA -> commit#N 或 owner/repo#N 且未出现 issue/pr 语义 -> 先询问资源类型硬规则：
-R owner/repo#123 自动当成 issue 或 PRgit showread
low-write
high-write
高风险确认模板：
即将执行高风险 GitHub 操作：
- repo: owner/repo
- resource: <issue|pr|release>
- identifier: <N|tag>
- action: <create|close|reopen|merge>
- extra impact: <merge strategy / delete branch / publish release>
请确认是否继续。
优先使用 --json 获取结构化信息并输出摘要；只在日志或交互式场景下使用纯文本输出。
gh issue view N -R owner/repo --json number,title,state,author,assignees,labels,comments,urlgh issue list -R owner/repo --state open --limit 20 --json number,title,state,labels,assignees,updatedAt,urlgh search issues QUERY --repo owner/repo --json number,title,state,updatedAt,urlgh issue create -R owner/repo --title "..." --body "..."gh issue comment N -R owner/repo --body "..."gh issue edit N -R owner/repo --title "..." --body "..." --add-label "bug"gh issue close N -R owner/repogh issue reopen N -R owner/repogh pr view N -R owner/repo --json number,title,state,author,assignees,labels,reviewDecision,mergeable,statusCheckRollup,urlgh pr list -R owner/repo --state open --limit 20 --json number,title,reviewDecision,updatedAt,urlgh search prs QUERY --repo owner/repo --json number,title,state,updatedAt,urlgh pr checks N -R owner/repo --json name,state,workflow,linkgh pr comment N -R owner/repo --body "..."gh pr review N -R owner/repo --approve|--request-changes|--comment --body "..."gh pr edit N -R owner/repo --title "..." --body "..." --add-label "bug" --add-reviewer reviewergh pr create -R owner/repo --base main --head branch --title "..." --body "..."。若分支尚未推送或需要本地整理提交，先转交 skills/git/SKILL.mdgh pr close N -R owner/repogh pr reopen N -R owner/repogh pr merge N -R owner/repo --squash|--merge|--rebasegh run view RUN_ID -R owner/repo --json status,conclusion,jobs,urlgh run view RUN_ID -R owner/repo --log-failedgh run rerun RUN_ID -R owner/repogh run rerun RUN_ID -R owner/repo --failedgh run watch RUN_ID -R owner/repo --compact --exit-statusgh release view TAG -R owner/repo --json tagName,name,isDraft,isPrerelease,publishedAt,urlgh release create TAG -R owner/repo --title "..." --notes "..."gh release edit TAG -R owner/repo --title "..." --notes "..."gh repo view owner/repo --json nameWithOwner,description,defaultBranchRef,viewerPermission,urlgh api repos/owner/repo/commits/SHA## GitHub Intent
<resource + action + risk>
## Target
repo: <owner/repo>
resource: <issue|pr|workflow_run|release|repo|commit>
identifier: <N|tag|sha|none>
## Command
`gh ...`
## Result
<关键结果摘要>
## Next Step
<继续执行 / 等待确认 / 停止原因>
---
status: <success|partial|blocked>
risk: <read|low-write|high-write>
gh 未安装：提示安装并停止gh auth login 并停止gh auth refresh -s <scope> 并停止owner/repogh 子命令和参数Use when handling local Git CLI daily operations such as checking status or diff, staging files, creating conventional commits, restoring local changes, reverting commits, or resolving merge/rebase/cherry-pick conflicts.
Use when explaining code, answering technical questions, comparing approaches, or providing repository-grounded analysis without entering an implementation or remediation workflow.
Use when evaluating system architecture, platform design, or high-level technical structure to identify production risks, evidence gaps, and prioritized remediation without directly redesigning or implementing the system.
Use when improving internal code structure without intentionally changing externally observable behavior, such as module splits, simplification, dependency cleanup, or maintainability and performance-oriented restructuring.
Use when feature ideas, issues, stakeholder notes, or partial specs need to be reviewed and turned into a concise, testable PRD with clear scope, user stories, acceptance criteria, and explicit open decisions.
Use when a PRD, feature spec, or acceptance criteria already exist and need to be turned into a concise test plan and traceable test cases with clear priorities, coverage, and execution focus.