pr

Analyze current branch changes and create GitHub pull requests with titles and descriptions.

Updated Jan 1, 2012
One-click install
npx skills add https://github.com/ysk1031/dotfiles --skill pr-ysk1031
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr
Source: https://github.com/ysk1031/dotfiles/tree/main/claude/skills/pr
Command: npx skills add https://github.com/ysk1031/dotfiles --skill pr-ysk1031

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub pull requests by analyzing your current branch changes, drafting a concise title and description, and opening the PR for review.

Core Features & Use Cases

  • Analyze current branch changes to draft PR content.
  • Interactively confirm or edit the suggested title and body.
  • Create the PR on GitHub with an optional --draft flag.
  • Push changes to the remote and open the PR.

Quick Start

Tell me to create a PR (for example, PR作って) and I will analyze your branch, propose a title and description, and create the PR after your confirmation.

Frequently Asked Questions about pr

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

FAQPage Schema
How do I automate GitHub pull request creation from my current branch?

You can automate GitHub pull request creation by instructing the tool to analyze your current branch, draft a title and description, push changes to the remote, and return the PR URL after confirmation.

Can I open a draft PR automatically from a feature or bugfix branch?

Yes, you can open a draft PR automatically by using the optional draft flag when initiating pull request creation for your feature or bugfix workflows.

Does the PR generation process require manual confirmation before opening?

Yes, the PR generation process requires interactive confirmation, allowing you to review and edit the suggested title and body before it pushes and creates the pull request.

How does automated PR creation determine the correct base branch on GitHub?

Automated PR creation determines the correct base branch by analyzing your current Git branch context, ensuring the pull request targets the appropriate destination branch.

What is the best way to generate a PR title and description from code changes?

The best way to generate a PR title and description from code changes is using an automation Skill that analyzes your branch diffs and drafts the content interactively for your review.