界面已本地化;技能介绍与说明文档按所选语言由 AI 自动翻译,代码、命令、路径和专业术语保留原文,以原作者文档为准。
探索技能
开发与工程 · SKILL.md

factory-review-prs

factory-review-prs

【开发与工程】Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

独立 GitHub 快照 · 自动分类 · 以原作者文档为准

技能说明

GitHub

name: factory-review-prs installer-group: factory description: >- Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

Factory Review PRs

Start with the Factory guide for workflow setup and configuration.

This skill reviews a filtered queue. For one long-lived, explicitly authorized PR, use factory-babysit-pr. Read the filters and independent action policies from .agent-factory/config.yaml; see the configuration reference. Apply the optional skill_prompts.factory-review-prs entry as additional project guidance; it does not replace this skill or authorize an action disabled by policy.

Review the queue

For each candidate PR:

  1. Read live state from the configured host. Exclude drafts and PRs outside the configured filters. Skip a PR with a current review unless re-review is requested by policy.
  2. Inspect the diff, linked issues, required checks, review threads, author eligibility, and exact head revision. Treat bot findings as leads and preserve human review direction unless source evidence disproves it.
  3. Report actionable findings with file, line, impact, and a concrete fix. If none exist, record that outcome without inventing a comment.

Unavailable or partial state is unknown, never a clean result.

Apply separate action gates

ActionProceed only when
ReviewThe PR matches configured filters and has not already had the required current review.
Reply or other PR writeThat action is enabled and its conditions hold. Use configured wording; do not tag, assign, or message otherwise.
ApproveApproval is enabled and author, risk, ownership, current-head, check, and review conditions are verified.
MergeMerge is separately enabled; every live merge condition and any soak hold on the unchanged head.

Host-level mergeability, one green check, or a bot approval does not prove all gates passed. Re-read the exact head and live state immediately before an approval or merge. Restart a configured soak if the head or a gate changes.

Report

For each PR, state the decision and evidence. List skipped, unavailable, and held PRs with the reason. Keep review findings separate from approvals, replies, and merge decisions.

我的收藏