메뉴
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
Use when a task needs a written execution plan with explicit steps, risks, verification, and user approval before implementation starts.
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
Use when a pull request already has review feedback that needs triage, code changes, verification, and clear replies back to reviewers.
Use when deciding whether a change is ready to merge and a concise cross-language checklist is more useful than a full narrative review.
Use when a pull request needs a serious pre-merge review covering correctness, edge cases, security, tests, documentation, and architecture.
| name | github |
| version | 1.0.0 |
| description | Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata. |
| activation | {"keywords":["github","issues","pull request","repository","commit","branch"],"exclude":["gitlab","bitbucket"],"patterns":["list.*issues","show.*issue","get.*issue","create.*issue","list.*pull","create.*pull","get.*repo","list.*branches","list.*commits"],"tags":["git","code-review","devops"],"max_context_tokens":2000} |
Prefer the GitHub plugin when it is available. Otherwise prefer the gh CLI for authenticated operations in this repository. Only use the REST API directly when the environment explicitly supports injected GitHub credentials.
Before doing any write action:
gh auth status succeeds if you plan to use the CLI.gh Commandsgh issue list --state open --limit 100
gh issue view <number> --json number,title,body,labels,comments,assignees,milestone
gh issue create
gh issue comment <number> --body "<text>"
gh pr list --state open --limit 100
gh pr view <number> --json number,title,body,author,files,labels,reviews,comments,statusCheckRollup
gh pr diff <number>
gh pr checkout <number>
gh pr create
gh pr comment <number> --body "<text>"
gh pr review <number> --comment --body "<text>"
gh repo view --json name,owner,defaultBranchRef
gh api repos/{owner}/{repo}/branches
gh api repos/{owner}/{repo}/commits
Use direct API calls only when the environment supports them.
https://api.github.comAccept: application/vnd.github+jsonAuthorization header unless the environment explicitly requires manual auth.per_page=100 for paginated endpoints.gh over raw HTTP when both are available.