Pull Request Creation

VerifiedSafe

Creates pull requests with a standardized format including summary, changes, and test plan. Helps maintain consistency in PR descriptions and ensures all necessary information is included for review. Invoke when you need to open a PR or submit changes for review.

Sby Skills Guide Bot
DevelopmentBeginner
6/2/2026
Claude Code
#pull-request#github#git#code-review

Recommended for

Automated summary

This skill creates a pull request on GitHub with a structured description.

Strengths

  • Automates PR creation with a clear format
  • Ensures code is pushed and tracked
  • Includes a summary, change list, and test plan

Limitations

  • Requires the user to have already committed and pushed
  • Depends on the gh tool being installed and configured
  • Does not handle reviews or merges
When to use it

Use this skill when you have finished your changes and want to submit a well-formatted pull request.

When not to use it

Do not use it if you haven't committed your changes locally yet or if you prefer to create the PR manually on the web interface.

Security analysis

Safe
Quality score90/100

The skill only uses git and gh commands for creating pull requests, with no destructive or exfiltrating actions. It operates within a standard development workflow.

No concerns found

How this analysis is made

Examples

Create a PR for a feature branch
Create a pull request for my current branch with summary 'Add user authentication' and mention issue #42.
Create a PR with custom description
Open a PR with title 'Fix login bug' and description listing the changes I made.
Create a PR after pushing
I've pushed my changes, now create a pull request targeting the main branch.

name: pr description: Create a pull request. Invoke when user wants to open a PR, create a pull request, or submit changes for review. allowed-tools: Bash(git:), Bash(gh:)

Pull Request

Create pull requests with clear descriptions.

PR Format

## Summary
<Brief description of what changed and why>

## Changes
<Bullet points of key changes>

## Test Plan
<How to verify this works>

Rules

  • NEVER mention code was generated by Claude
  • Title under 72 characters
  • Link related issues if applicable
  • Ask before creating if unsure about target branch

Process

  1. Ensure all changes committed and pushed
  2. Push with tracking if needed (git push -u origin <branch>)
  3. Create PR with gh pr create

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/pull-request-creation-mmio70sr/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/pull-request-creation-mmio70sr' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/pull-request-creation-mmio70sr/download' --output '.skill-downloads/pull-request-creation-mmio70sr/SKILL.md.part' && mv '.skill-downloads/pull-request-creation-mmio70sr/SKILL.md.part' '.skill-downloads/pull-request-creation-mmio70sr/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

Tools declared by the author (check availability in your agent): Bash(git:*), Bash(gh:*)

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/pull-request-creation-mmio70sr/SKILL.md' && test -s '.skill-downloads/pull-request-creation-mmio70sr/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/pr' && cp -R '.skill-downloads/pull-request-creation-mmio70sr' '.claude/skills/pr'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/pull-request-creation-mmio70sr'

openskills read 'pull-request-creation-mmio70sr'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/pull-request-creation-mmio70sr/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills