メニュー
Use when open pull requests need a read-only dashboard showing review state, scope, blockers, conflicts, and merge readiness.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | triage-prs |
| version | 1.0.0 |
| description | Use when open pull requests need a read-only dashboard showing review state, scope, blockers, conflicts, and merge readiness. |
| activation | {"patterns":["triage.*prs","triage.*pull requests"],"keywords":["prs","pull requests","triage"],"max_context_tokens":2500} |
Use this skill for a read-only pull request dashboard.
gh auth status succeedsgh pr list.For each PR, determine:
Flag:
Return a dashboard with:
Use 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 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.