github-pr-workflow

Manage GitHub pull request lifecycle with branch creation, CI monitoring, and merging.

Updated Jun 17, 2026

Search Tags:#automation #git #ci/cd #github #merge #pull-requests

Ready to run

npx skills add https://github.com/cxnaive/hermes-agent-llbot --skill github-pr-workflow-cxnaive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/cxnaive/hermes-agent-llbot/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/cxnaive/hermes-agent-llbot --skill github-pr-workflow-cxnaive

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the friction of managing GitHub pull requests by providing a unified, automated workflow for branching, committing, CI monitoring, and merging.

Core Features & Use Cases

Unified Workflow: Seamlessly switch between the GitHub CLI (gh) and standard git/curl commands based on your environment.
Automated CI Management: Monitor CI status, diagnose failures, and auto-fix common issues like linting or test errors.
Use Case: When a CI build fails, the agent can automatically fetch the logs, identify the error, apply a fix, and push the update to trigger a re-run.

Quick Start

Use the github-pr-workflow skill to create a new pull request for the current branch with the title feature add user authentication.

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 GitHub pull request lifecycle management from branch creation to merge?▼

Automating GitHub pull request workflows involves unifying branch creation, commit standardization, CI status monitoring, and automated merging. This skill manages the end-to-end lifecycle by integrating GitHub Actions and API-based repository management to eliminate manual friction.

Can I automatically fix CI failures and trigger a re-run for my GitHub pull request?▼

You can automatically fix CI failures by fetching build logs, identifying errors, and applying fixes for common issues like linting or test failures. Once the fix is pushed, it triggers a CI re-run automatically within the GitHub workflow.

Do I need the GitHub CLI installed to monitor CI status and automate pull request merges?▼

You do not strictly need the GitHub CLI, as standard git and curl commands are supported for full operational capability. However, the skill seamlessly switches to the GitHub CLI for API-based repository management when it is available in your environment.

What is the best way to standardize commits and manage branches for GitHub pull requests?▼

The best way to standardize commits and manage branches is through a unified workflow that seamlessly switches between the GitHub CLI and standard git commands based on your environment. This ensures consistent commit standardization across the PR lifecycle.

How do I create a new pull request for my current branch with a specific title?▼

To create a new pull request for the current branch, you instruct the workflow to generate it with your desired title. The skill handles the API or CLI calls required to publish the PR with the specified naming convention.

What are the limitations of using curl and git instead of the GitHub CLI for pull request automation?▼

Standard git and curl provide full operational capability for managing pull requests, but lack the seamless environment integration of the GitHub CLI. Relying on curl requires manual API endpoint management for actions like automated merging and CI monitoring.