create-pr

Analyze branch diffs and create GitHub Pull Requests via gh CLI.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/Suniljit/personal-toolkit --skill create-pr-suniljit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/Suniljit/personal-toolkit/tree/main/.opencode/skills/create-pr
Command: npx skills add https://github.com/Suniljit/personal-toolkit --skill create-pr-suniljit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automate the GitHub PR workflow by analyzing the current branch diffs, generating a concise summary, and guiding a safe push to create the PR after user confirmation.

Core Features & Use Cases

  • Analyze diffs between the current branch and the target base to produce a clear PR summary.
  • Prompt for user confirmation before pushing and creating the PR.
  • Create the PR via GitHub CLI with a well-structured title and description, supporting stacked branches and target branch specification.

Quick Start

Ask me to generate a PR summary for the current branch, review the changes, and push to create the PR.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I automatically generate a GitHub pull request summary from my branch diffs?

To generate a GitHub pull request summary, this Skill analyzes the git diffs between your current feature branch and the target base, creating a concise title and body for the PR. It then prompts for confirmation before pushing the changes.

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

Yes, you need both the git and gh CLI tools installed and available in your environment to automate pull request creation. The Skill relies on the GitHub CLI to push the branch and officially create the PR on your repository.

Can I create a pull request from a stacked branch targeting a specific base branch other than main?

Yes, you can create a pull request from stacked branches by specifying a target base branch other than main. The Skill analyzes the diffs against your specified target branch and generates the corresponding PR summary.

How does this approach handle PR creation safely without automatically pushing unwanted changes?

This approach handles PR creation safely by generating a diff summary and explicitly prompting for user confirmation before pushing. You can review the analyzed changes and the generated title and body before the push and PR creation occur.

What is the best way to create a pull request from terminal diffs without manually writing the description?

The best way to create a pull request from terminal diffs without manual writing is using an automation Skill that analyzes branch differences and generates a structured title and body. It compiles the diff data into a readable summary for GitHub CLI submission.

Why does my automated pull request workflow require a target branch selection?

Your automated pull request workflow requires target branch selection to accurately analyze the correct git diffs and apply changes to the intended base. Selecting the wrong target can merge unintended changes or fail to capture the correct feature branch differences.