pr

Create a pull request for the current branch using `gh`.

brave/brave-core2 installsMPL-2.0Synced Aug 25

Works with

Claude CodeCursorCodex CLIGitHub CopilotGemini CLI
---
name: pr
description: Create a pull request for the current branch using `gh`.
license: MPL-2.0
---

# Create Pull Request

Create a pull request for the current branch using `gh`.

## Current State

- Branch: !`git branch --show-current`
- Commits on branch: !`git log master..HEAD --oneline`
- Changed files: !`git diff master...HEAD --stat`

## Steps

### 1. Gather context

- Review the commits and changed files above.
- Check if the branch is associated with a GitHub issue (look at branch name,
  commit messages, or recent context for an issue number).

### 2. Push the branch

Run `git push -u origin HEAD`.

### 3. Create the PR

Use `gh pr create` with:

- **Title:** Short, direct summary of the change (under 70 chars).
- **Body:** A brief, factual summary of what changed and why. No filler. If
  there is an associated issue, include
  `Fix https://github.com/brave/brave-browser/issues/<number>` on its own line
  at the top of the body.

Keep the description concise. Just state what was done.

### 4. Done

Print the PR URL for the user.

More Code Review skills

pr-to-video

heygen-com/hyperframes

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.

178.9k

receiving-code-review

obra/superpowers

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

178.0k

public-relations

coreyhaines31/marketingskills

When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.

33.1k

← All Code Review skills

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY