mcpbeat

Pr

brave/pr

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

268 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3472
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/brave/brave-core --skill pr

The instruction itself

7 sections, as written by the author

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.

How to use it

Copy the folder

Take brave/pr from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.