github-pr-workflow

Automate the GitHub Pull Request lifecycle from branch creation to merging.

1|Updated Apr 29, 2026

Search Tags:#CI/CD #Git #GitHub #Pull Request #Automation #Merge

Ready to run

npx skills add https://github.com/bailynlove/STARK-TOWER --skill github-pr-workflow-bailynlove

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/bailynlove/STARK-TOWER/tree/main/opencrew/skills/github/github-pr-workflow
Command: npx skills add https://github.com/bailynlove/STARK-TOWER --skill github-pr-workflow-bailynlove

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, curl, python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire GitHub Pull Request lifecycle, from branch creation and code commit to PR creation, CI monitoring, auto-failure fixes, and merging, saving developers time and reducing manual errors.

Core Features & Use Cases

Automated PR Workflow: Handles branch creation, code commits, PR creation, CI/CD checks, auto-failure fixes, and merging.
CI Monitoring: Tracks CI/CD status and provides tools for monitoring and auto-resolving failures.
Merge Automation: Offers options for auto-merging PRs when all checks pass.
Use Case: Ideal for teams that want to streamline their code review and merge process, reducing the time spent on manual tasks and ensuring a smooth PR workflow.

Quick Start

Run the skill to start the GitHub Pull Request workflow for your current branch.

Frequently Asked Questions about github-pr-workflow

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

FAQPage Schema

How do I automate GitHub Pull Request creation and merging?▼

It tracks CI/CD status, monitors checks, and provides tools for auto-resolving failures during the Pull Request workflow, ensuring a smooth path to merging when all checks pass.

Do I need the GitHub CLI installed to automate PR workflows?▼

No, it supports GitHub CLI but falls back to using git and the GitHub REST API via curl to automate the Pull Request lifecycle if the CLI is unavailable.

What's the best way to handle CI/CD failures before merging a Pull Request?▼

Use merge automation with CI monitoring to track CI/CD status and apply auto-failure fixes before merging, ensuring Pull Requests only merge when all checks pass successfully.

Can I auto-merge a GitHub Pull Request when all CI checks pass?▼

Yes, merge automation offers options for auto-merging Pull Requests when all CI/CD checks pass, reducing manual intervention in the code review and merge process.

What are the requirements to automate the GitHub PR lifecycle?▼

You need authentication with GitHub and a local git repository configured with a GitHub remote to execute the automated Pull Request workflow successfully.