github-pr-workflow

Automate the GitHub pull request lifecycle from branch creation to merging.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill github-pr-workflow-marblesodas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/MarbleSodas/Mavis/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill github-pr-workflow-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you reliably manage the full GitHub Pull Request lifecycle—creating branches and commits, opening and monitoring PRs, diagnosing CI failures, and merging—without getting stuck when tooling (like gh) isn’t available.

Core Features & Use Cases

  • Branch, commit, and PR creation: Create a feature branch following conventional naming, craft conventional commits, push the branch, and open a PR using either gh or GitHub API (curl).
  • CI monitoring and feedback loop: Check PR checks, poll until completion, and interpret results to decide next actions.
  • CI auto-fixing workflow: Identify failing workflow runs, fetch and inspect logs, apply fixes to the repo, and retry CI up to a bounded number of attempts before escalation.
  • PR merging strategies: Perform squash/merge/rebase merges, delete branches after merge, and (when applicable) enable auto-merge via GraphQL.

Quick Start

Use the github-pr-workflow skill to create a PR for a change on your current branch, wait for CI to finish, and merge it once all checks are successful.

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 feature branches, pushing commits, opening draft or labeled PRs, polling combined and check-run status, and applying merge strategies once checks pass.

Can I fetch and debug failing GitHub Actions logs automatically when CI fails?▼

Yes, the workflow identifies failing GitHub Actions runs, fetches and inspects CI logs, applies fixes to the repository, and retries CI up to a bounded number of attempts before escalating.

What's the best way to enable auto-merge for GitHub pull requests when checks pass?▼

The best way to enable auto-merge is by utilizing GraphQL API requests to configure auto-merge settings when supported, allowing PRs to merge automatically once all required status checks are successful.

Do I need the GitHub CLI installed to create and monitor pull requests?▼

No, you do not need the GitHub CLI installed; the workflow handles GitHub authentication with a gh fallback to Git and curl APIs for branch creation, PR monitoring, and merging operations.

How does a CI auto-fixing workflow handle failed status checks on a pull request?▼

A CI auto-fixing workflow handles failed status checks by extracting logs from failed check runs, applying code fixes, pushing updates to the existing branch, and rechecking status in a repeatable loop.

What GitHub pull request merging strategies can I use after CI checks complete?▼

After CI checks complete successfully, you can perform squash, merge, or rebase merging strategies, delete branches after merge, and enable auto-merge when the repository configuration supports it.