github-pr-workflow

Automate GitHub PR lifecycles from branch creation to merge.

14|2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/gquthier/CLAWG --skill github-pr-workflow-gquthier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/gquthier/CLAWG/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/gquthier/CLAWG --skill github-pr-workflow-gquthier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end lifecycle of GitHub pull requests, from branch creation through PR, review, CI checks, and merging, reducing manual overhead and miscoordination.

Core Features & Use Cases

  • PR lifecycle automation: create branches, open PRs, monitor CI checks, auto-fix failures, and merge.
  • Flexible tooling: works with gh CLI when available, with a git + curl fallback for environments without gh.
  • Use Case: A software team can standardize PR workflows across multiple repos with minimal setup and predictable outcomes.

Quick Start

Create or switch to a feature branch, then run the workflow to manage PRs from branch creation to merge.

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 PR lifecycle from branch creation to merge?

Automate the GitHub PR lifecycle by creating branches, opening pull requests, monitoring CI checks, and merging automatically. This reduces manual overhead and miscoordination across standard git repository workflows from start to finish.

Can I automate pull request checks without the GitHub CLI installed?

Yes, you can automate pull request checks without the GitHub CLI. The workflow supports a git and curl fallback for environments lacking gh, ensuring CI monitoring and automated fixes still function in standard git repositories.

What do I need to set up before automating PR workflows in my git repository?

Automating PR workflows requires a GitHub remote, proper authentication, and repository access. Once these prerequisites are met, you can standardize pull request processes across multiple repositories with minimal setup.

Does this PR workflow automation handle CI check failures and apply automated fixes?

PR workflow automation handles CI check failures by applying automated fixes. It monitors continuous integration status during the pull request lifecycle and attempts to resolve issues before proceeding to the final merge.

What is the best way to standardize pull request workflows across multiple repositories?

Standardizing pull request workflows across multiple repositories is best achieved by automating the end-to-end lifecycle. Teams can use gh or curl-based workflows to ensure predictable outcomes and minimal setup for every PR.