Catalog
BuilderIO/factory-review-prs

BuilderIO

factory-review-prs

Experimental workflow for reviewing configured repositories' pull requests. Use for manual or scheduled PR triage, approval, or merge decisions.

v1.0LATEST
NewUpdated Sep 24, 2026

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

Action Proceed only when
Review The PR matches configured filters and has not already had the required current review.
Reply or other PR write That action is enabled and its conditions hold. Use configured wording; do not tag, assign, or message otherwise.
Approve Approval is enabled and author, risk, ownership, current-head, check, and review conditions are verified.
Merge Merge 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.

Files1
1 files · 1.0 KB

Select a file to preview

Overall Score

78/100

Grade

B

Good

Grades are signals, not a certification. Always review a skill yourself before use.

Safety

82

Quality

74

Clarity

82

Completeness

67

Summary

This skill guides AI agents to review pull requests from configured repositories according to policy-driven filters and action gates. It reads PR state from a host, analyzes diffs and review metadata, reports findings, and conditionally applies approval or merge decisions based on explicitly configured policies in `.agent-factory/config.yaml`.

Detected Capabilities

read PR metadata from configured hostanalyze PR diffs and code changesread review comments and check statusesevaluate eligibility gates (author, risk, ownership, checks)write PR reviews conditionallywrite PR approvals conditionallyexecute PR merges conditionallyread configuration from .agent-factory/config.yaml

Trigger Keywords

Phrases that agents use to match this skill to user intent.

review pull requeststriage pr queuepr approval workflowmerge gated decisionsscheduled pr review

Risk Signals

INFO

Conditional approval and merge execution based on configured policy gates

Review the queue, Apply separate action gates, Report sections
INFO

Reads live PR state from configured host (no destructive operations documented)

Review the queue section, step 1
INFO

PR write actions (reply, approve, merge) are gated by explicit policy configuration

Apply separate action gates table
INFO

Configuration-driven behavior — action scope determined by .agent-factory/config.yaml, not hardcoded

Read the filters and independent action policies section

Referenced Domains

External domains referenced in skill content, detected by static analysis.

github.com

Use Cases

  • Triage pull requests from multiple repositories on a schedule
  • Evaluate PR code changes against team policies before approval
  • Conditionally approve or merge PRs based on configured risk and ownership gates
  • Report actionable code findings without inventing spurious comments
  • Enforce review requirements and check statuses before merge

Quality Notes

  • Clear action gates documented in table format — approval and merge require explicit policy verification
  • Distinguishes between read operations (review findings) and write operations (approvals/merges), with separate conditions for each
  • Instructs agent to verify live state immediately before approval or merge, and to restart soak timers if conditions change — good safeguard against stale decisions
  • References configuration schema explicitly (`.agent-factory/config.yaml`, `skill_prompts.factory-review-prs`), allowing users to control scope and enable/disable actions
  • Scope limited to filtered queue; drafts and previously-reviewed PRs are excluded unless re-review is requested
  • Does not document what happens if config is malformed, missing, or inaccessible — edge case handling could be stronger
  • No explicit mention of how 'required checks' are interpreted (required by whom — GitHub branch protection, custom CI, etc.)
  • Skill emphasizes that bot findings are leads only and human review direction is preserved — good guidance for autonomous decision-making
Model: claude-haiku-4-5-20251001Analyzed: Sep 24, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Use BuilderIO/factory-review-prs in your dev environment

Command Palette

Search for a command to run...