Pr Agent Skill

by brave

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

268 tokens

context cost

the whole folder, loaded on every use

files

instructions only

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.

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

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

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

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.