github-pr-workflow

Name: github-pr-workflow
Availability: InStock
Author: thisismynewfmail-ui

Automate GitHub pull request creation, monitoring, and merging via gh CLI.

Updated Apr 12, 2026

Search Tags:#automation #git #github #cli #ci #pull-request

Ready to run

npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill github-pr-workflow-thisismynewfmail-ui

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-pr-workflow
Source: https://github.com/thisismynewfmail-ui/Monika-agent/tree/main/skills/github/github-pr-workflow
Command: npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill github-pr-workflow-thisismynewfmail-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Developers often spend time manually handling the many steps of a pull request—creating branches, committing, opening PRs, monitoring CI, fixing failures, and merging—especially when the gh CLI is unavailable.

Core Features & Use Cases

Branch & Commit Automation: Quickly create feature branches and make conventional commits.
PR Creation & Monitoring: Open pull requests via gh or fallback curl commands and watch CI status.
Auto‑Fix Loop: Detect CI failures, fetch logs, apply patches, and re‑run checks.
Merge Strategies: Perform squash, rebase, or regular merges, optionally enable auto‑merge.

Quick Start

Ask Monika to run the github‑pr‑workflow skill to open a new pull request for the current changes.

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 from the command line?▼

You can automate the GitHub pull request lifecycle from branch creation to merge by utilizing the gh CLI or falling back to the GitHub REST API via curl commands.

Can I monitor and automatically fix CI failures after opening a pull request?▼

Yes, the PR automation workflow monitors CI status, detects failures, fetches logs, applies patches, and re-runs checks automatically until the pipeline succeeds.

Do I need the gh CLI installed to automate my git pull request workflow?▼

No, you do not need the gh CLI strictly installed; the workflow uses the GitHub REST API with curl as a fallback for opening and merging pull requests.

What is the best way to handle branch creation and conventional commits before opening a PR?▼

The best way to handle branch creation and conventional commits is through automated branch generation, which structures feature branches and commits before opening the pull request.

Does this PR automation support squash, rebase, and auto-merge strategies?▼

Yes, the PR automation supports squash, rebase, and regular merge strategies, and can optionally enable auto-merge to finalize the pull request lifecycle.

Why do I need a GitHub token when automating pull requests with the REST API?▼

A GitHub token is required for API authentication when automating pull requests via the REST API fallback, ensuring your git operations and merges are authorized.