pr

Create and split Pull Requests across codebase layers using Git and GitHub CLI.

Updated Jul 5, 2026
One-click install
npx skills add https://github.com/xkl2013/lobe --skill pr-xkl2013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/xkl2013/lobe/tree/main/.agents/skills/pr
Command: npx skills add https://github.com/xkl2013/lobe --skill pr-xkl2013

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation and splitting of Pull Requests across layers, ensuring safe and organized code merges.

Core Features & Use Cases

  • Automated PR Creation: Generate PRs with the appropriate branch, title, and body content.
  • PR Splitting: Break down multi-layer changes into separate PRs for safe and sequential merges.
  • Use Case: When working on a cross-layer feature, this Skill can split a single branch into several PRs, ensuring that lower-level layers like the server contract are merged first.

Quick Start

Use the pr skill to create a new Pull Request for your current branch.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I split a single branch into multiple pull requests for different layers?

To split a branch for pull request creation, this Skill automates breaking down multi-layer changes into separate PRs, ensuring structured and sequential merges like merging server contracts first.

Do I need GitHub CLI and Gitmoji to automate pull request creation?

Yes, you need Git, GitHub CLI, and Gitmoji to automate pull request creation and splitting across layers, as these tools are required to manage branch operations and PR formatting.

What is the best way to manage cross-layer code merges safely?

The best way to manage cross-layer code merges safely is using automated PR splitting, which breaks down complex features into separate pull requests for sequential merging.

How does automated PR splitting handle lower-level layers like server contracts?

Automated PR splitting handles lower-level layers by generating separate pull requests that ensure foundational layers like server contracts are merged before higher-level dependencies.

Can I generate a single pull request with an appropriate branch and body automatically?

Yes, you can generate a single pull request automatically, as this Skill creates PRs with the appropriate branch, title, and body content for your current code changes.