github-pr-workflow

Manages GitHub pull requests from creation through merge with Git CLI/API and conventional commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the full GitHub pull request lifecycle so you can create branches, make commits, open PRs, monitor CI, fix failures, and merge with far less context switching.

Core Features & Use Cases

  • Branch and commit workflow: Create feature, fix, docs, refactor, or ci branches and write conventional commits that are easy to review and trace.
  • PR creation and review operations: Open pull requests with GitHub CLI or fall back to GitHub API calls, add reviewers and labels, and manage PR states.
  • CI monitoring and recovery: Check workflow status, inspect failing logs, diagnose common breakages, and iterate on fixes until checks pass.
  • Merge and cleanup: Squash merge, enable auto-merge, delete branches, and return to a clean main branch after completion.

Quick Start

Ask for a complete GitHub pull request workflow for my current branch, including commit guidance, PR creation, CI monitoring, failure recovery, and merge steps.

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 a GitHub pull request workflow from branch creation to merge?

You can automate a GitHub pull request workflow by creating feature branches, writing conventional commits, opening PRs via GitHub CLI, monitoring CI checks, and performing a squash merge to clean up the branch.

What's the best way to fix failing CI checks before merging a GitHub pull request?

To fix failing CI checks, inspect the failing workflow logs, diagnose common breakages, iterate on code fixes, and push commits until checks pass before merging the GitHub pull request.

How do I write conventional commits for a feature branch before opening a pull request?

Writing conventional commits involves using structured prefixes for feature, fix, docs, or refactor branches to ensure commit messages are easy to review and trace before opening a pull request.

Do I need the GitHub CLI to manage pull request states and add reviewers?

You can use the GitHub CLI to manage pull request states and add reviewers, but you can also fall back to standard GitHub REST and GraphQL API calls if the CLI is unavailable.

Can I enable auto-merge and delete branches after a pull request workflow completes?

Yes, you can enable auto-merge, perform a squash merge, delete the feature branch, and return to a clean main branch after the pull request workflow and CI checks complete successfully.

Why use conventional commits in a pull request workflow automation process?

Using conventional commits in a pull request workflow ensures that commit history remains structured, reliable, and easy to trace during collaboration and automated CI remediation.