Sponsor Suno AI Music arrow_forward
Slash Command

Pr Create

Create pull request with auto-generated template and description

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What Pr Create is

Pr Create is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

Pr Create gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install Pr Create

Claude Code

  1. Download pr-create.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/packages/devops-automation-pack/plugins/01-git-workflow/commands/pr-create.md, shared under the repository's MIT license. Read the full file on GitHub.

Automatically creates a GitHub pull request with AI-generated title and description based on your branch's commits and changes.

When to Use This

  • Ready to create PR for your feature branch
  • Want professional PR description without manual writing
  • Need to include commit history in PR description
  • Following team's PR template
  • DON'T use if gh CLI not installed

How It Works

You are a GitHub pull request expert who creates professional, informative PR descriptions. When user runs /pr-create or /gpr:

  1. Check prerequisites:
   # Verify gh CLI is installed
   which gh || echo "gh CLI required"

   # Verify user is authenticated
   gh auth status
  1. Analyze current branch:
   # Get current branch name
   git branch --show-current

   # Get base branch (usually main/master)
   git symbolic-ref refs/remotes/origin/HEAD | sed 's@^refs/remotes/origin/@@'
  1. Gather commit information:
   # Get commits in this branch (not in base)
   git log origin/main..HEAD --oneline

   # Get detailed commit messages
   git log origin/main..HEAD --format="%s%n%b"
  1. Analyze changes:
   # Get file statistics
   git diff origin/main..HEAD --stat

   # Identify affected areas
   git diff origin/main..HEAD --name-only
  1. Generate PR title:
  • If single commit: Use commit message as title
  • If multiple commits: Summarize common theme
  • Format: Action verb + specific change
  • Max 72 characters
  • Examples: "Add OAuth2 authentication", "Fix memory leak in data processor"
  1. Generate PR description:

Structure:

   ## Summary
   [2-3 sentences describing what this PR does and why]

   ## Changes
   - [Bullet point for major change 1]
   - [Bullet point for major change 2]
   - [Bullet point for major change 3]

   ## Testing
   - [How this was tested]
   - [Test cases covered]

   ## Related Issues
   Closes #[issue-number]
  1. Ask for confirmation: "Create PR with this title and description? (yes/no/edit)"
  1. Create PR:
   gh pr create --title "[title]" --body "[description]"
  1. Display PR URL:
    Pull request created: https://github.com/owner/repo/pull/123

Required Information

  • Current branch: Must be on feature branch (not main/master)
  • Commits: At least 1 commit ahead of base branch
  • gh CLI: GitHub CLI must be installed and authenticated

If prerequisites not met:

 Cannot create PR

Reason: [specific issue]
Solution: [how to fix]

Output Format

Present PR preview for confirmation:

Title: Add OAuth2 Google authentication

Description:
## Summary
Implements OAuth2 authentication flow using Passport.js, allowing users
to sign in with their Google account instead of creating a password.

## Changes
- Added Passport.js Google OAuth2 strategy
- Created /auth/google and /auth/google/callback routes
- Updated user schema to support OAuth providers
- Added Google Client ID/Secret to environment config

## Testing
- Manual testing with Google OAuth flow
- Unit tests for auth routes (95% coverage)
- Integration tests for user creation
…

Create this PR? (yes/no/edit)

Examples

Example 1: Single commit PR

User: /gpr

Current branch: feature/add-search Commits: 1 commit ahead

  • "feat(search): add global search functionality"

You:

Title: Add global search functionality

Description:
## Summary
Implements full-text search across products, users, and orders with
real-time suggestions.

## Changes
- Added SearchBar component with real-time autocomplete
- Implemented search API endpoint (/api/search)
- Added search indexing for products, users, orders

## Testing
- Manual testing with various search queries
- Unit tests for search algorithm
- Performance testing with 10,000 records

## Related Issues
…

Create this PR? (yes/no/edit)

Example 2: Multiple commits PR

User: /gpr

Current branch: fix/memory-leak Commits: 3 commits ahead

  • "fix(api): close database connections properly"
  • "perf(cache): implement connection pooling"
  • "test: add memory leak regression tests"

You:

Title: Fix memory leak in API layer

Description:
## Summary
Resolves memory leak caused by unclosed database connections. Implements
connection pooling to improve performance and prevent resource exhaustion.

## Changes
- Fixed database connection cleanup in API handlers
- Implemented connection pooling (max 10 connections)
- Added connection lifecycle logging
- Added regression tests to prevent future leaks

## Testing
- Memory profiling shows no leaks after 1000 requests
- Load testing with 100 concurrent users (stable memory)
- Regression tests added to CI pipeline
…

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Pr Create?

Pr Create is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Create pull request with auto-generated template and description

How do I install Pr Create in Claude Code?

Download pr-create.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use Pr Create in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is Pr Create safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.