split-ralph

Split a completed Git branch into independent pull requests using a plan file.

Updated Apr 1, 2021
One-click install
npx skills add https://github.com/danielukea/.dotfiles --skill split-ralph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: split-ralph
Source: https://github.com/danielukea/.dotfiles/tree/main/claude/.claude/skills/split-ralph
Command: npx skills add https://github.com/danielukea/.dotfiles --skill split-ralph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the complex process of splitting a large, completed feature branch into smaller, manageable pull requests, streamlining code review and integration.

Core Features & Use Cases

  • Automated Branch Splitting: Divides a single branch into multiple PRs based on defined groups in a plan file.
  • Commit Mapping: Intelligently maps commits to their respective PR groups, including handling review fixes.
  • Conflict Resolution: Provides strategies for resolving merge conflicts during the cherry-picking process.
  • Use Case: After completing a large feature on a ralph branch, use this Skill to automatically create separate PRs for each logical component or user story defined in your project plan, making reviews faster and less overwhelming.

Quick Start

Use the split-ralph skill to split the current branch using the plan file named 'project_plan.md'.

Frequently Asked Questions about split-ralph

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

FAQPage Schema
How do I split a Git branch into multiple pull requests?

Yes, you can automate branch splitting for code review by using a plan file to map commits to independent PR groups. This process divides a completed feature branch into smaller, manageable pull requests, handling conflict resolution during cherry-picking.

How does commit mapping work when automating pull request creation?

Commit mapping works by intelligently matching commits from your completed branch to their respective PR groups defined in a plan file. It also handles review fixes and provides strategies for resolving merge conflicts during the cherry-picking process.

Do I need a plan file to split branches into independent pull requests?

Yes, you need a plan file to split branches into independent pull requests. The Skill uses this plan file to map commits to PR groups and determine specified base branches, ensuring the automated branch splitting aligns with your project's logical components or user stories.

What is the best way to handle merge conflicts when splitting a feature branch?

The best way to handle merge conflicts when splitting a feature branch is to use the conflict resolution strategies provided during the cherry-picking process. This ensures commits are accurately mapped to their respective PR groups without manual intervention.

Can I break down a large feature branch into smaller code review units?

Yes, you can break down a large feature branch into smaller code review units. The Skill divides a single completed branch into multiple pull requests based on defined groups in a plan file, making reviews faster and less overwhelming.