pr-create

Create GitHub pull requests from branch plan documents using the GitHub CLI.

1|Updated Nov 18, 2023
One-click install
npx skills add https://github.com/CherrySalmon/tyto --skill pr-create-cherrysalmon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-create
Source: https://github.com/CherrySalmon/tyto/tree/main/.claude/skills/pr-create
Command: npx skills add https://github.com/CherrySalmon/tyto --skill pr-create-cherrysalmon

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the creation of GitHub pull requests by intelligently extracting relevant information from your branch plan, ensuring clear and structured descriptions for reviewers.

Core Features & Use Cases

  • Automated PR Description: Generates a PR description based on your branch plan's problem statement, changes, design notes, and test results.
  • Branch Plan Integration: Reads and interprets specific sections of your branch plan (CLAUDE.<branch-name>.md) to populate the PR details.
  • Use Case: After completing a feature developed following a detailed branch plan, use this Skill to push your code and create a PR with a comprehensive, well-organized description, saving you manual writing time and improving review clarity.

Quick Start

Use the pr-create skill to push the current branch and create a pull request targeting the main branch.

Frequently Asked Questions about pr-create

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

FAQPage Schema
How do I automate GitHub pull request creation from a branch plan document?

To automate GitHub pull request creation, this Skill extracts structured information like problem statements, changes, and test results from your branch plan document to generate a comprehensive PR description and push the branch using the GitHub CLI.

What is the best way to generate a structured PR description from development notes?

The best way to generate a structured PR description is to parse specific sections of your branch plan document, extracting design notes and test results to populate the title and body of the pull request automatically.

Do I need the GitHub CLI installed to automate pull request creation?

Yes, you need the GitHub CLI installed, because this Skill depends on the gh command-line tool to push the current branch to the remote repository and create the pull request.

Can I target a specific base branch when creating a pull request from a branch plan?

Yes, you can target a specific base branch when creating a pull request, allowing you to direct your automated PR creation towards branches like main or any other target specified in your workflow.

How does branch plan integration work for populating pull request details?

Branch plan integration works by reading and interpreting specific sections of your CLAUDE.<branch-name>.md document, using the extracted problem statement, changes, design notes, and test results to build the PR title and body.

What should I do if my pull request description is missing test results from my branch plan?

If your pull request description is missing test results, ensure your branch plan document contains the expected structured sections for test results, as the Skill extracts these specific sections to populate the PR body.