managing-pull-requests

Automate GitHub pull request creation, rebasing, labeling, and review triggers.

Updated Aug 18, 2025
One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill managing-pull-requests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: managing-pull-requests
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/managing-pull-requests
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill managing-pull-requests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill streamlines GitHub Pull Request workflows by automating PR creation, base-branch synchronization, and review requests, reducing manual overhead and human errors.

Core Features & Use Cases

  • Automates PR creation using a standardized template and deterministic titles/bodies.
  • Synchronizes the base branch with rebase to minimize merge conflicts.
  • Applies labeling by inferring related issues and architecture, and triggers auto-review workflows.
  • Supports end-to-end PR management from draft to merge-ready state.

Quick Start

Create a pull request from your feature branch using the standard template and labels.

Frequently Asked Questions about managing-pull-requests

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

FAQPage Schema
How do I automate pull request creation and sync branches in GitHub?

Automating pull request creation uses standardized templates and deterministic titles to eliminate manual overhead, while synchronizing the base branch with rebase minimizes merge conflicts in GitHub workflows.

What is the best way to coordinate code reviews across multiple branches?

Coordinating code reviews across multiple branches is best handled by triggering auto-review workflows and automatically applying inferred labels based on related issues and architecture.

Can I automatically apply labels to a pull request based on related issues?

Yes, you can automatically apply labels to a pull request by inferring related issues and architecture, which helps trigger appropriate auto-review workflows without manual intervention.

Does this PR automation work with draft states and transition them to merge-ready?

This PR automation supports end-to-end management, transitioning a pull request from an initial draft state directly to a merge-ready state using deterministic PR generation.

Why use automated rebase synchronization before creating a pull request?

Using automated rebase synchronization before creating a pull request ensures your feature branch is updated with the base branch, minimizing merge conflicts and reducing human errors during integration.