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
806/2/2026
Claude Code
#pull-request#github#git#code-review

Recommended for

Our review

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

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
Related skills