github-pr-workflow

Automate the GitHub Pull Request lifecycle using gh CLI or git and REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the entire GitHub Pull Request lifecycle, from creating branches and committing changes to opening Pull Requests, monitoring CI status, auto-fixing failures, and merging. It integrates with the gh CLI and falls back to git + GitHub REST API.

Core Features & Use Cases

  • Branch Creation: Automate the creation of feature branches following standard naming conventions.
  • Commit Making: Automate the commit process with conventional commit messages and proper staging of files.
  • PR Creation: Open Pull Requests with detailed descriptions and issue references.
  • CI Monitoring: Monitor the CI/CD pipeline status and check for failures.
  • Auto-Fixing: Automatically fix common CI failures, including test failures and linting issues.
  • Merging: Merge Pull Requests using squash or rebase strategies.
  • Use Case: For developers who want to automate their GitHub workflow and ensure their PRs are smoothly merged into the main branch.

Quick Start

Run the skill to automate the PR lifecycle for a new feature branch named 'feat/new-feature'.

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

You can automate the GitHub Pull Request workflow by using the gh CLI or git combined with the GitHub REST API. This handles branch creation, commits, PR opening, CI monitoring, auto-fixing failures, and merging automatically.

Can I automatically fix CI failures when monitoring a GitHub Pull Request?

Yes, you can automatically fix common CI failures during Pull Request monitoring. The automation detects test failures and linting issues, applies fixes, and commits the changes to ensure the PR merges smoothly.

Do I need the gh CLI to automate GitHub Pull Requests with git?

No, you do not strictly need the gh CLI to automate GitHub Pull Requests. While the automation uses the gh CLI primarily, it can fall back to using git and the GitHub REST API via curl to manage the entire PR lifecycle.

What's the best way to automate conventional commits and feature branch creation for GitHub?

The best way to automate conventional commits and feature branch creation is using an automation script that follows standard naming conventions. It stages files, generates conventional commit messages, and opens PRs with detailed descriptions.

Does automated GitHub PR merging support both squash and rebase strategies?

Yes, automated GitHub PR merging supports both squash and rebase strategies. You can configure the automation to merge Pull Requests using your preferred strategy to maintain a clean main branch commit history.

Why does my automated Pull Request workflow require authentication with GitHub?

Your automated Pull Request workflow requires GitHub authentication to authorize branch creation, PR opening, CI monitoring, and merging actions. You need a local git repository and valid GitHub credentials to execute these operations.