skills.rest
mitchlabeetch
mitchlabeetchCOMMUNITY
Explore all skills by this author →
GitHub

pr-automation

Automate GitHub pull request review and merge readiness workflows.

Updated Aug 23, 2026
Search Tags:#workflow#github#labeling#ci#pull-request#pr-automation
One-click install
npx skills add https://github.com/mitchlabeetch/Largarda --skill pr-automation-mitchlabeetch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-automation
Source: https://github.com/mitchlabeetch/Largarda/tree/main/.agents/skills/pr-automation
Command: npx skills add https://github.com/mitchlabeetch/Largarda --skill pr-automation-mitchlabeetch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill automates the end-to-end PR review and merge readiness workflow, reducing manual triage and speeding up contributions.

Core Features & Use Cases

  • Single heavy action per session: review OR fix, then exit to avoid long-running tasks.
  • Robust PR selection and state-machine labeling: claims PRs with mutex labels, handles wake-up on CI failures, rebase and conflict resolution, and routes to human review when needed.
  • Deterministic workflow with audit-friendly steps: fetch candidates, apply label states, run CI checks, re-review when necessary, and post decisions to PRs.

Quick Start

Invoke the /pr-automation command to start processing open PRs and advance them toward merge readiness.

Frequently Asked Questions about pr-automation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub pull request reviews and merge readiness workflows?▼

Automating GitHub pull request reviews involves polling open PRs, applying label state transitions, evaluating CI status, running fix loops, and posting merge decisions. This skill executes one heavy action per session to process pull requests toward merge readiness safely.

What is the best way to handle CI failures and conflicts during PR automation?▼

The best way to handle CI failures and conflicts during PR automation is using a deterministic state machine that wakes up on CI failures, attempts auto-rebase for conflict resolution, and applies label state transitions. Unresolved conflicts are routed to human review.

Does this PR automation workflow support long-running continuous review loops?▼

This PR automation workflow does not support long-running loops; it operates under a strict one-heavy-action-per-session rule, executing either a review or a fix before exiting. It polls candidate PRs, applies state labels, and hands off remaining work to subsequent sessions.

How do I prevent race conditions when multiple automated processes review the same pull requests?▼

Prevent race conditions during PR automation by using mutex labels to claim pull requests. The state machine applies these label state transitions to ensure only one automated process executes a heavy action or review on a specific PR at a time.

When should I route automated pull request reviews to a human reviewer?▼

Route automated pull request reviews to human reviewers when the deterministic state machine encounters unresolved merge conflicts, exhausts auto-rebase attempts, or detects persistent CI failures that exceed automated fix loop capabilities during the PR processing workflow.

Related Skills

Explore More Software Engineering Skills→
yusaduymazyusaduymaz

gsd-inbox

Triage GitHub issues and pull requests against repository templates and guidelines.

Community
Intermediate
overviewlabsoverviewlabs

github-pr-workflow

Automate GitHub pull request lifecycle from branch creation to merge.

Community
Advanced
limit5limit5

SKILL_HD_VENDOR_REBASE

Automate initial patch rebase conflict resolution attempts during HD vendor code integration workflows.

Community
Basic
legglegg

agents-sdk

Develop, configure and deploy AI agents on Cloudflare Workers with routing and durable execution.

Community
Advanced