github-pr-workflow

Automate GitHub pull request creation, commits, and merging via CLI or REST API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually orchestrating branch creation, commits, pull‑request submission, CI monitoring, auto‑fixing failures and merging is time‑consuming and error‑prone, especially when the gh CLI is unavailable.

Core Features & Use Cases

  • Branch & Commit Automation: Create feature branches, stage changes, and commit with conventional messages.
  • Pull Request Management: Open PRs via gh or fallback to git + GitHub REST API, add reviewers, labels, and draft mode.
  • CI Status Monitoring & Auto‑Fix: Watch GitHub Actions checks, diagnose failures, and apply automated fixes before merging.
  • Merge Strategies: Perform squash, rebase, or regular merges, enable auto‑merge, and clean up branches.

Quick Start

Ask the agent to create a new feature branch, commit your changes, open a pull request and merge it once CI passes.

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 creation and merging end-to-end?

You can automate the GitHub pull request lifecycle by using an agent to create feature branches, commit changes, open PRs, monitor CI checks, and execute squash, rebase, or regular merges once checks pass. This eliminates manual orchestration errors.

Can I open a pull request using git and the GitHub REST API if the gh CLI is unavailable?

Yes, pull request management supports opening PRs via the `gh` CLI with an automatic fallback to git and the GitHub REST API. This ensures branch creation and PR submission succeed even when the `gh` CLI is not installed.

Do I need a GitHub token to automate branch management and CI monitoring?

Yes, automating branch management, CI monitoring, and merge operations requires a configured GitHub token or an authenticated `gh` CLI to interact with GitHub endpoints and execute automated pull request workflows.

How does CI status monitoring handle GitHub Actions check failures before merging?

CI status monitoring watches GitHub Actions checks, diagnoses failures, and applies automated fixes to the pull request before merging. This ensures broken code is resolved automatically without manual intervention.

What is the best way to manage merge strategies and enable auto-merge for GitHub pull requests?

Managing merge strategies involves using automation to perform squash, rebase, or regular merges, enable auto-merge upon CI pass, and clean up branches post-merge. This streamlines the pull request workflow completely.