github-pr-workflow

Automate GitHub PR workflows from branch creation to merging.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nadicodeai/argo-agent --skill github-pr-workflow-nadicodeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/nadicodeai/argo-agent/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/nadicodeai/argo-agent --skill github-pr-workflow-nadicodeai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Streamlines the GitHub Pull Request lifecycle by providing a structured, repeatable workflow from feature branch creation through PR submission, review, CI checks, and merge operations, reducing manual overhead and improving consistency.

Core Features & Use Cases

  • Branch management and naming conformance for new features (feat/, fix/, refactor/ patterns)
  • End-to-end PR orchestration including PR creation, reviewer assignment, and merge strategy selection (merge, squash, rebase)
  • CI status monitoring and guidance, with fallback commands for environments without gh installed
  • Use cases include multi-repo collaborations, automated PR templates, and standardized merge criteria across teams

Quick Start

Create a feature branch, push it, and open a PR to trigger CI checks.

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?

Automating a GitHub pull request workflow involves orchestrating branch creation, PR submission, CI checks, and merge operations. This Skill structures the entire PR lifecycle using gh CLI and GitHub API fallback commands to reduce manual overhead.

What's the best way to manage feature branch naming conventions before opening a pull request?

Managing feature branch naming requires conforming to standardized patterns like feat/, fix/, or refactor/ before opening a pull request. This Skill enforces branch management and naming conformance automatically to maintain consistency across collaborative software projects.

Can I monitor CI status checks and automate merging after a pull request passes?

Monitoring CI status checks and automating merges after a pull request passes is fully supported. This Skill guides CI status monitoring and handles merge strategy selection, choosing between merge, squash, or rebase based on your project requirements.

Do I need the gh CLI installed to automate pull request generation and review?

You do not strictly need the gh CLI installed to automate pull request generation and review. This Skill provides GitHub API fallback commands for environments without gh, though configuring a GITHUB_TOKEN and a local git repository remains required.

How does PR orchestration handle reviewer assignment and standardized merge criteria?

PR orchestration handles reviewer assignment and standardized merge criteria by providing a structured workflow for multi-repo collaborations. This Skill automates reviewer assignment during PR creation and applies consistent merge criteria across teams.