generic-pr-merge

Automate the GitHub Pull Request lifecycle from local changes to main branch merge.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/Puzzle9900/puzzle9900-claude-plugin --skill generic-pr-merge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generic-pr-merge
Source: https://github.com/Puzzle9900/puzzle9900-claude-plugin/tree/main/skills/generic-pr-merge
Command: npx skills add https://github.com/Puzzle9900/puzzle9900-claude-plugin --skill generic-pr-merge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the entire process of taking local code changes through a GitHub Pull Request, including creation, merging, and local synchronization.

Core Features & Use Cases

  • End-to-end PR workflow: Automates branching, committing, pushing, PR creation, CI checks, and merging.
  • Error handling: Manages common issues like "not up to date" errors with rebase and force-push.
  • Use Case: When you have a set of changes ready for review and merging into the main branch, use this skill to handle all the Git and GitHub operations seamlessly.

Quick Start

Use the generic-pr-merge skill to create a pull request from your current changes.

Frequently Asked Questions about generic-pr-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a GitHub pull request from local changes to merge?

You can automate a GitHub pull request by using a skill that handles branch creation, staging, committing with co-authorship, pushing, PR creation with detailed body, CI check monitoring, squash merging, and local main branch synchronization.

What is the best way to handle not up to date errors during a git push?

To resolve not up to date errors during a git push, perform a rebase and then force-push your branch to synchronize local commits with the remote main branch before merging.

Can I monitor CI checks automatically before a pull request is merged?

Yes, automating the pull request lifecycle includes monitoring CI check monitoring, ensuring continuous integration passes before performing a squash merge into the main branch.

Does the full PR lifecycle workflow include local main branch synchronization?

Yes, the full PR lifecycle workflow includes local main branch synchronization, ensuring your local repository reflects the latest changes after the remote squash merge is completed.

How do I create a GitHub pull request with a detailed body automatically?

Automating PR creation generates a detailed body for your GitHub pull request, staging local changes, committing with co-authorship, and pushing to a new branch before opening the request.