pr-automation

Automate pull request reviews, fixes, CI checks, and merges.

33|6|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill pr-automation-gaogg521
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-automation
Source: https://github.com/gaogg521/1ONE-ClaudeCode/tree/main/.claude/skills/pr-automation
Command: npx skills add https://github.com/gaogg521/1ONE-ClaudeCode --skill pr-automation-gaogg521

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the PR lifecycle by polling open pull requests, applying reviews, executing fixes, and merging eligible changes to maintain development velocity.

Core Features & Use Cases

  • Automated PR lifecycle management: poll open PRs, determine eligibility, apply mutex labels, run reviews and fixes, and merge when trusted.
  • Deterministic task handling: processes at most one heavy action per invocation to ensure safe, incremental automation.
  • Use Case: Teams leveraging GitHub workflows can keep multiple PRs moving with minimal manual intervention while preserving human review for edge cases.

Quick Start

Invoke the PR automation workflow by issuing /pr-automation to begin processing open PRs in the repository.

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 merges?

Automate GitHub pull request reviews and merges by orchestrating a script-driven workflow that polls open PRs, applies reviews, executes fixes, and merges eligible changes from trusted contributors. This automated PR lifecycle management requires minimal manual intervention while preserving human review for edge cases.

Can I automatically merge pull requests only from trusted contributors?

Yes, you can automatically merge pull requests only from trusted contributors. The automation determines PR eligibility and applies mutex labels before executing heavy actions, safely merging changes when the contributor is trusted and CI checks pass.

How does CI status checking work with automated PR lifecycle management?

CI status checking works with automated PR lifecycle management by safely monitoring CI checks through a script-driven workflow. The automation processes at most one heavy action per invocation, ensuring safe, incremental CI validation and human handoffs before applying merges.

What is the best way to handle multiple open pull requests with minimal manual intervention?

The best way to handle multiple open pull requests with minimal manual intervention is using deterministic task handling. This automated workflow processes at most one heavy action per invocation, applying mutex labels to ensure safe, incremental automation across multiple PRs.

Do I need a specific repository setup to run automated PR fixes?

You need a repository with open pull requests and a SKILL.md file containing frontmatter name and description to run automated PR fixes. Optional scripts, references, and assets directories support on-demand tasks within the script-driven workflow.

Why does the PR automation process only one action at a time?

The PR automation processes only one action at a time to ensure safe, incremental automation through deterministic task handling. This approach safely manages labels, CI status, and human handoffs without overwhelming the repository's workflow.