pr

Creates and splits GitHub pull requests into ordered, layer-based stacks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of creating pull requests and splitting complex cross-layer changes into ordered, stacked PRs, ensuring safe and manageable code integration into the development branch.

Core Features & Use Cases

  • PR Creation: Automatically create a pull request for the current branch targeting the canary branch.
  • Branch Strategy: Handles uncommitted changes and merges, searches related GitHub issues, and uses predefined PR templates.
  • Stacked PRs: Split cross-layer features into ordered PRs for safe and sequential integration.
  • Use Case: When a feature spans multiple layers, this Skill ensures that backend changes are merged before UI changes, avoiding dependency conflicts.

Quick Start

Use the pr skill to create a pull request for the current branch with the default target of canary.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I split a cross-layer feature into stacked pull requests on GitHub?

To split a cross-layer feature into stacked pull requests, this Skill automates layer-based splitting to ensure backend changes merge before UI changes, preventing dependency conflicts. It sequences PRs for safe integration into the target branch.

How do I create a pull request for my current branch targeting the canary branch?

To create a pull request for your current branch targeting the canary branch, this Skill handles uncommitted changes and merges automatically. It searches related GitHub issues and applies predefined PR templates for structured submissions.

What is the best way to manage dependency conflicts when integrating cross-layer features?

Managing dependency conflicts during cross-layer integration is handled by splitting changes into ordered, stacked PRs. This ensures sequential merging, integrating backend changes before UI changes to avoid breaking dependencies.

Do I need GitHub API access to automate branch management and PR creation?

Yes, GitHub API access is required to automate pull request creation and layer-based splitting. This access allows the workflow to search related GitHub issues, handle merges, and manage branch strategy for cross-layer integration.

How are uncommitted changes handled when creating a pull request?

Uncommitted changes are handled automatically during pull request creation to ensure a clean merge. The Skill manages these pending modifications before searching related GitHub issues and applying predefined PR templates for structured integration.