pr-automation

Poll GitHub pull requests, apply labels, and advance eligible PRs through review and merge.

7|2|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/bitan-del/gods-eye-desktop --skill pr-automation-bitan-del
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-automation
Source: https://github.com/bitan-del/gods-eye-desktop/tree/main/.claude/skills/pr-automation
Command: npx skills add https://github.com/bitan-del/gods-eye-desktop --skill pr-automation-bitan-del

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This PR automation orchestrator reduces manual toil by polling open pull requests, assigning bot labels, and advancing eligible PRs through review and merge.

Core Features & Use Cases

  • Automated PR triage: discovers open PRs, prioritizes readiness, and applies bot:reviewing or bot:fixing labels to coordinate automation.
  • CI-aware processing: waits for CI results, handles wake-ups for snoozed PRs, and re-queues as needed to keep progress flowing.
  • Human handoff with traceability: posts review results, maintains atomic label updates, and logs decisions for audit.

Quick Start

Invoke the /pr-automation command to start automated PR processing.

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 PR reviews and merging?

To automate GitHub PR reviews and merging, this Skill polls open pull requests, assigns bot labels, and advances eligible PRs through review and merge by checking CI status and handling conflicts without manual intervention.

What is the best way to handle snoozed PRs and CI wait times in an automated workflow?

Handling snoozed PRs and CI wait times in an automated workflow requires polling open requests, waiting for CI results, and re-queuing snoozed wake-ups to keep progress flowing while maintaining atomic label updates.

How do I ensure my automated PR merge process is audit-friendly?

To ensure your automated PR merge process is audit-friendly, the workflow enforces atomic label changes, posts review results as comments on GitHub, and records every decision log for human review.

Can I use this PR automation to triage fresh pull requests with merge conflicts?

Yes, you can use this PR automation to triage fresh pull requests with merge conflicts. It discovers open PRs, prioritizes readiness, applies bot labels, and specifically handles merge conflicts to keep the workflow moving.

Does automated PR triage work without manual intervention for CI status checks?

Automated PR triage works without manual intervention for CI status checks by polling GitHub data, waiting for CI results, and advancing eligible PRs through review and merge only when CI passes.