skills.rest
zangjeicy
zangjeicyCOMMUNITY
Explore all skills by this author →
GitHub

github-pr-workflow

Automate GitHub pull request lifecycle with branch management, commit standardization, CI monitoring, and merging.

Updated Jul 13, 2026
Search Tags:#automation#git#ci/cd#github#merge#pull-requests
One-click install
npx skills add https://github.com/zangjeicy/Hermes --skill github-pr-workflow-zangjeicy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/zangjeicy/Hermes/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/zangjeicy/Hermes --skill github-pr-workflow-zangjeicy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and templates (resource) components.

What problem does it solve?

This skill removes the friction from managing GitHub pull requests by automating the repetitive steps of branching, committing, CI monitoring, and merging.

Core Features & Use Cases

  • Unified Workflow: Provides a consistent interface for PR management regardless of whether the GitHub CLI (gh) or standard git/curl commands are available.
  • Automated CI Handling: Includes a robust loop for monitoring CI status, diagnosing failures, and auto-fixing common issues like linting or test errors.
  • Use Case: When a developer needs to push a feature branch, create a PR, monitor CI checks, and squash-merge upon success, this skill handles the entire sequence with minimal manual intervention.

Quick Start

Use the github-pr-workflow skill to create a new pull request for the current branch and monitor its CI status until completion.

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 branching to merging?▼

Automating the GitHub pull request lifecycle involves a unified workflow that manages branch creation, commit standardization, CI status monitoring, and automated squash-merging upon success.

How can I monitor CI status and auto-fix failing checks on a pull request?▼

Monitoring CI status uses a robust loop to track checks, diagnose failures, and auto-fix common issues like linting or test errors before completing the pull request merge process.

Do I need the GitHub CLI installed to manage pull requests automatically?▼

You do not need the GitHub CLI installed; the workflow provides fallback mechanisms using standard git and curl commands for environments lacking the gh CLI tool.

What authentication is required to automate pull request merging?▼

Automating pull request merging requires authenticated access to GitHub repositories, which can be configured via API tokens or standard GitHub CLI configuration settings.

Can I standardize commits and squash-merge pull requests automatically?▼

Yes, you can standardize commits and squash-merge pull requests automatically by triggering the end-to-end workflow that enforces commit rules and merges upon successful CI completion.

What are the limitations of automating pull requests without the GitHub CLI?▼

Without the GitHub CLI, the automation relies on standard git and curl commands as a fallback, which may limit advanced repository interactions compared to the native gh CLI integration.

Related Skills

Explore More Software Engineering Skills→
tile-aitile-ai
346

tilelang-github-operations

Install GitHub CLI and create pull requests via authenticated workflows.

Official
Advanced
willietranwillietran
3

merge

Squash-merge successful session worktrees into the feature branch sequentially.

Community
Intermediate
dhamijadhamija

gap-resolver

Prioritize LLM user-testing gaps and drive fix-verify cycles.

Community
Advanced
musical-basicsmusical-basics

github-issues

Create and manage GitHub issues via gh CLI or REST API.

Community
Intermediate