github-pr-workflow

Automate GitHub pull request lifecycle with CI monitoring and merging.

Updated May 15, 2026
One-click install
npx skills add https://github.com/cabezno/bmb-encover-agent --skill github-pr-workflow-cabezno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/cabezno/bmb-encover-agent/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/cabezno/bmb-encover-agent --skill github-pr-workflow-cabezno

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of managing the full GitHub Pull Request lifecycle—creating branches, committing changes, opening PRs, monitoring CI, fixing failures, and merging—without getting stuck on tool differences between gh and raw git/curl.

Core Features & Use Cases

  • End-to-end PR lifecycle guidance: Branch creation, conventional-commit style commits, PR creation (gh or REST API), CI monitoring, and merging (squash/merge/rebase).
  • CI failure triage and remediation loop: Detect failing checks, fetch failed logs, apply code fixes using repo file-edit tooling, push, and re-check CI up to a practical retry limit.
  • GitHub owner/repo automation for API calls: Extracts owner/repo from the current git remote to correctly target REST/GraphQL endpoints.

Example use case: You push a feature branch, open a PR, see CI tests failing, then use this workflow to read the failing job logs, patch the code, re-run checks, and merge once green.

Quick Start

Use this workflow to create a branch, push it, open a PR, wait for CI, and merge the change with a squash merge.

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 the GitHub Pull Request lifecycle from branch creation to merge?

You can automate the GitHub Pull Request lifecycle by creating branches, committing changes with conventional commits, opening PRs via gh CLI or REST API, monitoring CI checks, and merging using squash, merge, or rebase methods.

Can I monitor CI status and auto-fix failing checks on a GitHub pull request?

Yes, you can monitor CI status and auto-fix failing checks by detecting failures, fetching failed job logs, applying code fixes, pushing changes, and re-checking CI up to a practical retry limit before merging.

Does this PR workflow work without the GitHub CLI installed?

Yes, this PR workflow works without the GitHub CLI by falling back to raw git commands and GitHub REST or GraphQL API calls to handle pull requests, CI monitoring, and merges.

What GitHub authentication is needed to automate pull request merges?

To automate pull request merges, you need GitHub authentication via gh auth login, a GITHUB_TOKEN environment variable, or configured git credentials to access repository APIs and perform merge operations.

How does the workflow extract the owner and repository for GitHub API calls?

The workflow extracts the owner and repository automatically from the current git remote URL, ensuring REST and GraphQL API endpoints are correctly targeted for pull request and CI operations.

What are the limitations of automating GitHub PR merges with this approach?

A limitation is that auto-fixing CI failures relies on a practical retry limit, meaning complex test failures requiring human intervention may exceed the automated remediation loop and halt the merge process.