Pr
- 7 installs
- 3.5k repo stars
- Updated August 5, 2026
- brave/brave-core
pr is a Claude Code skill that creates a pull request for the current branch using the GitHub CLI, with a short title and a factual body.
About
Creates a pull request for the current branch using the GitHub CLI. It reviews the branch commits and changed files, checks for an associated GitHub issue, pushes the branch, and opens the PR with a short title and a factual body. A developer uses it to turn finished branch work into a PR without hand-writing the description.
- Pushes the current branch and opens a PR with gh
- Links an associated brave-browser issue when found
- Writes a short factual title and body, no filler
Pr by the numbers
- 7 all-time installs (skills.sh)
- Ranked #457 of 733 Git & Pull Requests skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
pr capabilities & compatibility
Free; requires the gh CLI.
- Capabilities
- code review
- Works with
- github
- Use cases
- code review
- Runs
- Runs locally
- Pricing
- Free
What pr says it does
Create a pull request for the current branch using `gh`.
Run `git push -u origin HEAD`.
npx skills add https://github.com/brave/brave-core --skill prAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 7 |
|---|---|
| repo stars | ★ 3.5k |
| Last updated | August 5, 2026 |
| Repository | brave/brave-core ↗ |
What it does
Open a pull request for the current branch using gh with a concise title and body.
Who is it for?
Developers who finished branch work and want a clean PR opened automatically.
When should I use this skill?
The current branch is ready to become a pull request.
What you get
The branch is pushed and a PR is opened with a concise title and factual body.
By the numbers
- 4-step flow (gather, push, create, done)
Files
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.
Related skills
Caveman CommitGenerate terse, Conventional Commits messages that preserve intent without fluff or AI attribution.272k94k
Resolving Merge ConflictsQuickly understand, resolve, and commit merge conflicts without losing work or breaking their flow.183k193kGit Guardrails Claude CodePrevent Claude Code from accidentally running destructive git commands like force push, hard reset, or clean.175k193k
Using Git WorktreesGuarantee every new feature or implementation task runs inside a clean, isolated workspace without polluting the main branch or current working directory.149k263k
Git CommitGenerate accurate conventional commit messages and intelligently stage files directly from natural language requests.40.6k37.2k
Resolve Merge ConflictsQuickly understand and resolve Git merge conflicts without losing context or breaking changes.16.5k148