github-pr-workflow

Guide GitHub pull requests from branch creation through CI monitoring and merge.

4|Updated May 18, 2026
One-click install
npx skills add https://github.com/ZardLi1115/zedclaw --skill github-pr-workflow-zardli1115
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/ZardLi1115/zedclaw/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/ZardLi1115/zedclaw --skill github-pr-workflow-zardli1115

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It eliminates the guesswork of managing the full GitHub pull request lifecycle by providing a repeatable, command-based workflow for creating branches, opening PRs, monitoring CI, fixing failures, and merging safely.

Core Features & Use Cases

  • Branch, commit, and PR creation: Creates a feature branch, uses conventional commit messages, pushes to the remote, and opens a PR using gh or GitHub’s API.
  • CI visibility and monitoring: Checks combined status and GitHub Actions check runs, then provides polling guidance until CI completes.
  • Bounded CI auto-fixing loop: Guides diagnosing failed workflow runs, reading logs, applying code changes, pushing updates, and retrying up to a configured limit.
  • Merge options and cleanup: Supports squash/merge/rebase merges and deletes the branch afterward; includes guidance for enabling auto-merge.
  • Operational reference assets: Includes supporting documentation templates for CI troubleshooting and conventional commits to help produce consistent PRs and fixes.

Quick Start

Ask the agent to run the GitHub PR lifecycle for your current repository, including creating the branch, opening the PR, watching CI, and applying up to three fix attempts until checks pass.

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 workflow from branch creation to merge?

To automate the GitHub pull request workflow, this Skill guides you through creating a feature branch, opening a PR, monitoring CI status, applying bounded auto-fixes for failures, and merging safely using either the gh CLI or GitHub's REST/GraphQL APIs.

Can I use this to automatically fix failing GitHub Actions CI checks on my pull request?

Yes, you can automatically fix failing GitHub Actions CI checks. This Skill provides a bounded auto-fixing loop that reads workflow run logs, diagnoses failures, applies code changes, pushes updates, and retries CI up to a configured limit.

What is the best way to monitor GitHub PR CI status and trigger merge automation without the gh CLI?

The best way to monitor PR CI status without the gh CLI is by using GitHub token/API authentication. This Skill detects your available auth method and uses REST/GraphQL APIs to check combined status, poll check runs, and execute merge automation.

Do I need GitHub authentication and the gh CLI installed to manage pull request lifecycles?

You need GitHub authentication, but you do not strictly need the gh CLI. The Skill detects whether you are using gh CLI or token/API authentication and adapts its commands to extract the owner/repo and manage the pull request lifecycle accordingly.

How do I ensure consistent conventional commits when creating git branches for feature and refactor PRs?

To ensure consistent conventional commits for feature and refactor PRs, this Skill includes operational reference assets. These provide documentation templates for conventional commits and CI troubleshooting to help produce consistent PRs and code fixes.

What are the limitations of using merge automation for GitHub pull requests?

A limitation of this merge automation is the bounded auto-fixing loop, which stops retrying CI fixes after a configured limit. It supports squash, merge, and rebase strategies with branch cleanup, but requires successful CI evidence before final execution.