pr

Split branch changes into logical commits and draft a pull request.

7|3|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/flexphere/fude.nvim --skill pr-flexphere
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/flexphere/fude.nvim/tree/main/.claude/skills/pr
Command: npx skills add https://github.com/flexphere/fude.nvim --skill pr-flexphere

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of splitting a branch's changes into logical commits, executing those commits, and creating a draft pull request, reducing manual overhead and error-prone PR preparation.

Core Features & Use Cases

  • Commit splitting: Break a branch's changes into discrete commits aligned with logical changes.
  • Commit execution: Apply the prepared commits to the branch in a controlled sequence.
  • Draft PR creation: Generate a draft PR ready for review with templated messaging.
  • Use Case: When preparing a feature, this skill can systematically organize work into commits and produce a draft PR for faster review.

Quick Start

Split the current branch into logical commits, execute the commits, and draft a PR for review.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I split a branch's changes into logical commits before opening a pull request?▼

To split branch changes into logical commits, this skill analyzes your working branch, groups discrete changes, applies them in a controlled sequence, and generates a draft PR for review.

What is the best way to automate draft pull request creation from a feature branch?▼

Automating draft pull request creation involves coordinating commit planning, executing sequential commits on the branch, and using the GitHub CLI to generate a templated draft PR.

Do I need the GitHub CLI installed to create a draft pull request with this workflow?▼

Yes, you need the GitHub CLI installed. This workflow enforces both Git and GitHub CLI prerequisites to execute commit splitting and generate the draft pull request directly from your branch.

Can I organize feature branch commits automatically for better code review traceability?▼

Yes, you can organize feature branch commits to improve traceability. This skill breaks down branch changes into discrete, logical commits, helping reviewers track incremental changes.

Why split commits into a sequence when preparing a pull request?▼

Splitting commits into a sequence ensures each commit aligns with a logical change. This structure reduces manual overhead, minimizes error-prone PR preparation, and improves review quality.

What are the limitations of automating pull request preparation with this approach?▼

This approach is limited to standard software development workflows. It requires Git and GitHub CLI prerequisites, meaning it cannot execute or draft pull requests in environments lacking these tools.