ralph-pr

Create pull requests from completed tasks using GitHub CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/TravisBumgarner/claude-brain --skill ralph-pr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ralph-pr
Source: https://github.com/TravisBumgarner/claude-brain/tree/main/skills/ralph-pr
Command: npx skills add https://github.com/TravisBumgarner/claude-brain --skill ralph-pr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of pull requests for completed tasks, eliminating manual PR drafting and branch management.

Core Features & Use Cases

  • Automates PR creation by reading a SCOPES.yml, deriving the base branch from the milestone, and generating a task-specific branch name.
  • Builds a PR body that includes the task title, a Closes reference to the issue, a concise summary, and acceptance criteria.
  • Handles push and PR creation via GitHub CLI to streamline workflow for software teams.

Quick Start

Run the ralph-pr skill with a SCOPES.yml path and a task ID to generate and open the corresponding PR.

Frequently Asked Questions about ralph-pr

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

FAQPage Schema
How do I automate pull request creation for completed GitHub tasks?▼

Automate pull request creation by reading a SCOPES.yml file, deriving the base branch from a milestone, and executing gh pr create to open the PR with a structured title and body.

How does a SCOPES.yml file determine the base branch for a pull request?▼

The SCOPES.yml file determines the base branch by mapping task milestones to their respective base branches, allowing the PR automation to target the correct integration branch.

Can I automatically include acceptance criteria and issue references in a GitHub PR body?▼

Yes, you can include acceptance criteria and issue references in a GitHub PR body by automating the creation process to append a Closes reference, a concise summary, and the criteria directly into the PR text.

What is the best way to generate task-specific branch names from an issue ID and title?▼

Generate task-specific branch names by constructing a task-<id>-<slugified-title> branch format, which standardizes branch naming and automatically links the branch to its corresponding task.

Do I need the GitHub CLI to automate PR creation for completed tasks?▼

Yes, you need the GitHub CLI installed because the automation handles pushing changes and creates the pull request directly using the gh pr create command.