github-pr-workflow

Manage GitHub pull request lifecycles from branch creation through merge.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of managing a GitHub pull request from start to finish, so you can move from local changes to a merged branch with fewer manual steps and less context switching.

Core Features & Use Cases

  • Branch and commit flow: Create feature, fix, refactor, docs, ci, or chore branches and write conventional commits that clearly describe each change.
  • PR creation and review prep: Open pull requests with a consistent title and body, request reviewers, add labels, and use draft mode when work is still in progress.
  • CI monitoring and recovery: Check build and test status, inspect failing logs, diagnose common issues, and push fixes until the checks pass.
  • Merge and cleanup: Merge with squash, rebase, or merge commits, then delete the branch and return to main cleanly.
  • Use case: A developer finishes a feature and wants one guided workflow to commit the work, publish the branch, open the PR, watch CI, and merge it when ready.

Quick Start

Use the github-pr-workflow skill to guide me through creating a branch, committing my changes, opening a pull request, monitoring CI, and merging it in my current GitHub repository.

Frequently Asked Questions about github-pr-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage a GitHub pull request from branch creation to merge?

Managing a GitHub pull request involves creating a branch, committing changes, opening the PR, monitoring CI, and merging. This workflow automates the lifecycle from local changes to a merged branch with fewer manual steps and less context switching.

What is the best way to automate CI monitoring and failure diagnosis for pull requests?

Automating CI monitoring for pull requests involves checking build and test status, inspecting failing logs, diagnosing common issues, and pushing fixes until checks pass. This workflow polls status and handles failure recovery automatically.

Does this pull request workflow support both gh CLI and curl for API interactions?

Yes, this pull request workflow supports gh and git plus curl workflows. It handles remote owner and repo extraction, status polling, failure diagnosis, and token-based API fallback for environments lacking the standard CLI tools.

How do I prepare a code review using conventional commits and draft pull requests?

Preparing a code review involves creating feature, fix, or refactor branches with conventional commits, then opening pull requests with consistent titles, requesting reviewers, adding labels, and using draft mode for work in progress.

What are the options for merging and cleaning up a GitHub branch after CI passes?

Merging and cleaning up a GitHub branch offers squash, rebase, or merge commit strategies. After merging, the workflow deletes the branch remotely and returns the local environment cleanly to the main branch.