Agent Skills
› cobusgreyling/loop-engineering
› pr-review-triage
pr-review-triage
GitHub用于PR看护循环，对受监控的PR进行状态分类。评估CI检查、审查意见及合并就绪度，区分功能与行政状态，依据项目规范判断是否可合并，并建议相应操作或人工介入。
Trigger Scenarios
需要评估拉取请求的合并准备情况
执行PR看护循环以监控多个PR状态
判断PR是否存在阻塞性评论或冲突
Install
npx skills add cobusgreyling/loop-engineering --skill pr-review-triage -g -y
SKILL.md
Frontmatter
{
"name": "pr-review-triage",
"description": "Triage open pull requests for CI status, review comments, and merge readiness. Use in PR babysitter loops. Respects project review norms and required checks.\n",
"user_invocable": true
}
PR Review Triage Skill
For each watched PR, report:
Per-PR Output
### PR #N — title
- Checks: passing | failing | pending | absent/unknown — list names and conclusions
- Required-check policy: known and satisfied | known and unsatisfied | unknown
- Reviews: approved N | changes requested | review required | absent/unknown
- Mergeability: clean | conflicts | unknown
- Blocking comments: (list actionable ones)
- Ready to merge: yes | no — reason
- Suggested loop action: none | minimal-fix | rebase | escalate-human
Rules
- Zero checks, or no check runs/status contexts returned, means
absent/unknown, notpassing, unless the repository policy explicitly requires no checks. - Separate functional CI from administrative statuses such as a CLA or labeler; list both, but do not use administrative success as evidence that tests passed.
mergeableor a clean merge state only means Git found no conflict. It does not mean the PR is ready, reviewed, or verified.- "Ready to merge" requires a known project policy, every required check satisfied, required approvals present, no changes requested, no blocking comments, and no merge conflict.
- If the required-check or review policy cannot be established, report
Ready to merge: noand escalate to a human. - Non-actionable nits → note but do not spawn fix.
- If PR idle >4 days → suggest human handoff.
- High-risk labels (security, breaking) → escalate-human always.
Version History
-
07996dc
Current 2026-07-31 00:10
修复了将缺失/待定/仅行政类GitHub检查误判为通过的问题；细化检查状态为通过/失败/待定/未知，并要求策略明确且满足方可判定为可合并。
- e55bb6d 2026-07-05 11:07
