A Git and pull-request workflow that creates a branch, commits changes, pushes them to a remote repository, and opens a pull request. A branch is a separate line of code changes, while a pull request asks others to review them.

Use it to create feature, bug-fix, hotfix, spike, documentation, or refactoring branches, commit and push changes, and open a linked pull request.

It standardizes the steps for sending code changes for review and connects the work to related GitHub or Linear issues when project settings allow it.

brpr — Skill for Claude Code by feniix

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add feniix/pi-extensions --skill brpr

Clone the repo

git clone --depth 1 https://github.com/feniix/pi-extensions

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/feniix/pi-extensions/brpr/github.svg)](https://agentmods.dev/skills/feniix/pi-extensions/brpr)

Your own site

<a href="https://agentmods.dev/skills/feniix/pi-extensions/brpr"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/brpr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/feniix/pi-extensions/brpr"><img src="https://agentmods.dev/badge/skills/feniix/pi-extensions/brpr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,390 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.02390
Opus 5	$0.00024	$0.01195
Sonnet 5	$0.00010	$0.00478
Haiku 4.5	$0.00005	$0.00239

Measured 10d ago against content hash 7e0372959814, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

brpr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

packages/pi-devtools/skills/brpr/SKILL.md · 212 lines

How it starts

The opening of the file, as written. The whole thing — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Branch, Push, and PR Workflow

Creates a branch (if needed), commits changes, pushes, and opens a pull request. Links related issues from GitHub or Linear based on project tracker config.

Tool Restrictions (Critical)

Use ONLY these tools:

devtools_get_repo_info - Get current branch/status
devtools_create_branch - Create feature branch
devtools_commit - Stage and commit changes
devtools_push - Push to remote
devtools_create_pr - Create PR
Read - Read tracker config and PR templates
Glob - Find PR template files
Grep - Search for branch conventions
Write - Create tracker config file

Branch type reference

Default mapping from branch types to prefixes and conventional commit types. Both branch creation (step 2) and commit crafting (step 3) reference this table. If repo conventions (discovered in step 2a) define different prefixes or additional types, those override this table.

Type	Branch prefix	Conventional commit type
feature	`feature/` or `feat/`	`feat`
bug	`bugfix/`	`fix`
hotfix	`hotfix/`	`fix`
spike	`spike/`	`chore`
docs	`docs/`	`docs`
refactor	`refactor/`	`refactor`

Process

Step 1: Check Current State

Call devtools_get_repo_info to understand Pi's active working directory and worktree state:

Which active worktree and branch (or detached HEAD) are in use?
Is this a linked worktree?
Are there uncommitted changes in this working tree?

All workflow tools operate in that active working directory; do not infer state from another linked worktree.

If on detached HEAD, abort with: "You're in detached HEAD state. Please checkout a branch first."

On the default branch → continue to Step 2 (branch creation). The PR will target this branch.
On any other branch → skip to Step 3 (commit). The PR will target the default branch.

Step 2: Create Branch (if needed)

Only when on the default branch.

Read the full file on GitHub · 212 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 212 lines · 49 tokens per session scan A 7e0372959814

Subscribe to this mod's changes

brpr is a skill published in the GitHub repository feniix/pi-extensions (23 stars, last pushed 6d ago), licensed MIT. It adds 49 tokens to every session and 2,390 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Commits Git and workflow Releases TypeScript ai-agents coding-agents developer-tools mcp pi

pi-package-sandbox-test

Use when verifying that published Pi packages install and load for normal users, including pi.dev package compatibility checks, release validation, Daytona sandbox tests, and package installability audits.

spences10/my-pi · 40 tokens

agentplane-release-and-packaging-operator

Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.

basilisk-labs/agentplane · 60 tokens

pi-release-workflow

Use when preparing or validating Pi monorepo releases, including Changesets, pnpm lockfile updates, package previews, release-age policy, and installability checks.

spences10/my-pi · 38 tokens

pi-review-gated-delivery

Use when coordinating review-gated delivery of discrete GitHub issues between one implementation peer and a review-only lead, with user-owned Changesets and approval-gated commits.