create-pr

Create a GitHub pull request from the current git branch with a conventional title.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/FinderLost/easy-locker-web --skill create-pr-finderlost
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-pr
Source: https://github.com/FinderLost/easy-locker-web/tree/main/.claude/skills/create-pr
Command: npx skills add https://github.com/FinderLost/easy-locker-web --skill create-pr-finderlost

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines and standardizes creating a GitHub Pull Request from the current git branch by guiding branch selection, validating commits and diffs, preventing duplicate PRs, and generating a clear, review-ready title and description that follow project conventions.

Core Features & Use Cases

  • Interactive base selection: Prompts the user to choose the target branch (typically develop or main) and enforces branch policies for releases.
  • Commit and diff analysis: Instructs reviewing git log and diffs against the base branch to produce an accurate summary and motivation for reviewers.
  • Safety and workflow checks: Verifies there is no open PR for the same branch, ensures local changes are pushed (without force), and requires an authenticated GitHub CLI for PR creation.
  • Conventional title and descriptive body: Produces a conventional-commits-style title and a structured description that explains what, why, and any review focus or SEO impact notes.

Quick Start

Create a PR from the current branch targeting develop with a conventional-commit-style title and a clear descriptive body using the skill's prompts.

Frequently Asked Questions about create-pr

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

FAQPage Schema
How do I create a pull request with a conventional commit title and descriptive body from my current git branch?

To create a pull request, this Skill analyzes your git log and diffs against a base branch to generate a conventional-commits-style title and a structured description explaining what changed and why. It then uses the GitHub CLI to submit the PR.

How does git branch management prevent duplicate open pull requests when pushing local changes?

Branch management prevents duplicate pull requests by verifying if an open PR already exists for your current branch before proceeding. It ensures local commits are safely pushed to the remote repository without using force pushes.

Do I need an authenticated GitHub CLI to generate a PR description from my feature branch?

Yes, you need an authenticated GitHub CLI and access to the repository remote. The Skill relies on the CLI to validate commits, sync your local branch with the remote, and officially create the pull request.

What is the best way to prepare a release branch pull request while enforcing branch policies?

The best way to prepare a release pull request is using interactive base selection to target develop or main, enforcing branch policies. The Skill reviews diffs and flags SEO-impacting changes to ensure review readiness.

Why does pull request creation fail when my local branch is not synced with the remote repository?

Pull request creation fails if local changes are not pushed to the remote because the GitHub CLI requires a synced branch. The Skill performs safety checks to prevent force pushes and ensure your branch is up to date before creating a PR.