메뉴
Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | pr-shepherd |
| version | 1.0.0 |
| description | Use when a pull request needs one coordinated workflow covering review state, fixes, checks, branch updates, and merge readiness. |
| activation | {"patterns":["shepherd.*pr","manage.*pr"],"keywords":["pr","review","merge"],"max_context_tokens":3000} |
Use this skill when the user wants one workflow to handle a pull request from review through merge readiness.
gh auth status succeedsAGENTS.md defines the quality gate for the projectAGENTS.md.gh pr view.gh pr checkout.If the PR already has review comments:
If there are no comments or the user asked for a fresh review:
For each approved code change:
Run the checks defined in AGENTS.md in order. If a step fails, fix it and re-run.
Only recommend merge when:
Return these sections in order:
Use when a GitHub issue should be handled end-to-end, including issue analysis, code changes, tests, verification, and an optional commit.
Use when working with GitHub repositories, issues, pull requests, branches, or commits and the task needs authenticated repository operations or GitHub metadata.
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 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.