Factory Review Prs

From the author

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

— the description by Builder.io

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

Factory Review PRs is an experimental workflow designed to automate the triage and management of pull requests within configured repositories. It evaluates PRs against specific filters and policies defined in the project configuration, ensuring that reviews, approvals, and merge decisions are handled consistently. The skill emphasizes verifying live state and head revisions before taking any action, providing a structured approach to maintaining code quality and repository health.

What it does

Filters pull requests based on repository configuration and current state.
Inspects diffs, linked issues, and review threads for actionable findings.
Reports findings with specific file, line, and impact details.
Executes approval or merge actions only when all configured gates are met.
Maintains a clear separation between review findings and automated actions.
Handles skipped or held PRs by documenting the specific reason for the delay.

When to use it

When you need to automate the triage of incoming pull requests.
When you want to enforce consistent review and merge policies across repositories.
When you require a systematic way to check PR status against defined quality gates.
When you need to perform scheduled PR reviews or batch processing.

Advantages

Reduces manual effort in triaging and reviewing standard pull requests.
Ensures that merge decisions are based on verified live state and current head revisions.
Provides clear, evidence-based reporting for all review decisions.
Allows for flexible configuration of review and merge policies per repository.

Usage examples

“Review the current pull request queue for the repository.”: The agent scans the configured repository, filters PRs, inspects the diffs and status, and provides a report of findings or actions taken.
“Check if any PRs are ready for merge based on current policies.”: The agent verifies all merge gates, including head revision stability and check status, and proceeds with the merge if all conditions are met.

Install

Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/builderio/factory-review-prs/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip factory-review-prs.zip -d .agents/skills

Documentation by Builder.io

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:

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.
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.
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.

Files

ATTRIBUTION.mdAdded by AutoGineer861 B
LICENSELicence file added by AutoGineer1.0 KiB
SKILL.md2.4 KiB

SKILL.md