Agent skill

PR Update

by OutThisLife in OutThisLife/brooklyn-skills

Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff.

MITAuto-check: notesDevelopment

Install PR Update

skills CLI
$ npx skills add OutThisLife/brooklyn-skills --skill pr-update -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install OutThisLife/brooklyn-skills pr-update --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/OutThisLife/brooklyn-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/pr-update .claude/skills/pr-update && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
pr-update
GitHub stars
199
Token cost
~1.3k tokens
SKILL.md length
633 words
Files
1
Skills in repo
22
Repo updated
First seen
Licence
MIT

At a glance

Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff.

  • Works in 6 steps: git status / git diff / git log / git… → Detect an existing PR/MR for this branch… → Draft a title and body from all… → …
  • The user says /pr-update
  • SKILL.md covers Steps, Title + body, Commits and Preserve media (hard rule), plus 2 more sections
  • Calls git, gh and glab; reaches github.com

What it does

PR Update is an agent skill from OutThisLife/brooklyn-skills. Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff. Preserves any media already in the body. Use when the user says /pr-update, open a PR, update the PR, refresh the PR title/description, or wants the PR opener/manager flow.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Pull requests. It works with Git. The repository describes itself as: Skills that drive best-in-class engineering. The licence is MIT.

When your agent uses it

  • The user says /pr-update
  • Refresh the PR title/description
  • Wants the PR opener/manager flow

Example prompts

  • “/pr-update”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. git status / git diff / git log / git diff ...HEAD (and
  2. Detect an existing PR/MR for this branch (gh pr view / glab mr view).
  3. Draft a title and body from all commits/files in the PR, not one commit.
  4. If updating: fetch the current body first. Preserve every media item
  5. Apply with gh pr create / gh pr edit (or glab equivalents).
  6. End with the PR/MR as a markdown link — the number and the full forge

What it can do on your machine

Read from SKILL.md and the folder at commit 8a97904. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh
    • glab
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

PR Update loads about 1.3k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 633 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~73
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:73
    e formatting with logic, commit secrets/`.env`, or rewrite

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from OutThisLife/brooklyn-skills at commit 8a97904, republished under its MIT licence (© OutThisLife). 633 words, ~1,326 tokens.

Download SKILL.mdSave it as .claude/skills/pr-update/SKILL.md (or your agent's skills folder).
name
pr-update
description
Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff. Preserves any media already in the body. Use when the user says /pr-update, open a PR, update the PR, refresh the PR title/description, or wants the PR opener/manager flow.

PR Update (open or refresh)

One skill for create and update. Make the title + body match the branch as it is now. Do not strip media from an existing description.

Steps

  1. git status / git diff / git log / git diff <default>...HEAD (and remote tracking) so you know the full change set — not just the latest commit.
  2. Detect an existing PR/MR for this branch (gh pr view / glab mr view).
    • None → create (push upstream with -u if needed).
    • Exists → edit title + body in place. Do not open a duplicate.
  3. Draft a title and body from all commits/files in the PR, not one commit.
  4. If updating: fetch the current body first. Preserve every media item exactly (see below). Then rewrite text so Summary / Test plan (or the repo's usual sections) stay accurate.
  5. Apply with gh pr create / gh pr edit (or glab equivalents).
  6. End with the PR/MR as a markdown link — the number and the full forge URL ([#123](https://github.com/org/repo/pull/123), GitLab ! equivalent). Never a bare #123. This is the one place the rule is written down; the other skills just follow it.

Title + body

  • Title: concise, why-focused; match repo PR style when obvious.
  • Body: use the repo's template when one exists; otherwise:
markdown
## Summary
<1-3 bullets of what changed and why>

## Test plan
- [ ] <concrete checks>
  • Run the prose through no-tropes before publishing.
  • Do not invent reviewers, labels, or milestone unless asked.

Commits

Shape the branch's commits as part of opening/refreshing the PR.

  • Check effective user.name and user.email before committing. GitHub login does not set commit attribution. If email is unset or Git infers a local-host address, stop before publishing and confirm an account-associated email. Never publish after ignoring Git's inferred-identity warning.

  • One concern per commit. Default to a topical split (2–5 is typical) even if not asked; don't dump everything into one blob unless the user wants it.

  • Match the repo's recent commit style (git log --oneline -15); subject = why. No "WIP" / "fix stuff".

  • Rebuild with soft reset + path-staged commits (no git rebase -i — needs a TTY). Show the final git log --oneline <default>..HEAD before force-push. Two traps in that recipe:

    • Soft-reset to the branch's real base SHA (git merge-base HEAD origin/<default>), never to origin/<default> itself — it moves mid-task and will stage other people's commits as yours.
    • git reset <base> -- <path> leaves that path unstaged, so the next git commit silently captures its pre-edit version. Verify the content landed (git show <sha>:<path> | grep <new symbol>) before force-push.
  • Keep authorship when reshaping others' work (Co-authored-by / cherry-pick), especially during pr-triage salvage.

  • Don't mix pure formatting with logic, commit secrets/.env, or rewrite commits already on the default branch without asking.

Show full SKILL.md (207 more words)Show less

Preserve media (hard rule)

When a PR/MR already has a body, never delete media.

Treat as media (keep verbatim, same URLs/markup/order when possible):

  • Markdown images / links to images or video (![](...), [...](...) to media)
  • HTML <img>, <video>, <source>, <br> used between media blocks
  • GitHub/GitLab upload / user-attachments / moved-image URLs
  • Image/video-only paragraphs or HTML comments wrapping media

Update flow:

  1. Read the existing body. Extract JSON descriptions to plain Markdown with jq -r '.description' before using line-oriented file tools; one long escaped JSON string can be truncated even when the overall file fits. Reject truncated content rather than rebuilding a partial description.
  2. Extract and keep the media blocks.
  3. Rewrite textual sections so they match the current diff.
  4. Re-attach the preserved media (same block(s), typically at the end unless they were interleaved on purpose — then keep interleaving).
  5. Before submit, diff old body vs new: every media URL/markup from the old body must still be present.

If a refresh would drop media, stop and keep the old body (or only edit the title) rather than publishing a media-stripped description.

Scope

  • In: open PR/MR, push if needed for create, shape commits, retitle, rewrite description, preserve media, print URL.
  • Out: rebase, CI, and review threads (pr-ready), triage/salvage (pr-triage), merging.

Forge cheatsheet

bash
# GitHub — read
gh pr view --json url,title,body,baseRefName,headRefName

# GitHub — create
gh pr create --title "…" --body "$(cat <<'EOF'
…
EOF
)"

# GitHub — update (body from file avoids shell-eating newlines/media)
gh pr view --json body -q .body > /tmp/pr-body.md
# …edit /tmp/pr-body.md carefully…
gh pr edit --title "…" --body-file /tmp/pr-body.md

# GitLab
glab mr view
glab mr create
glab mr update <N> --title "…" --description-file /tmp/pr-body.md

© OutThisLife, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/pr-update of OutThisLife/brooklyn-skills.

Open the folder on GitHubat commit 8a97904

Compare with similar skills

PR Update next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

PR Update compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
PR Update this skillOutThisLife/brooklyn-skills199—~1.3kAutomated safety check: NotesMIT
Finishing a Development Branchobra/superpowers297k5 repos~1.9kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Open Code Review CLIalibaba/open-code-review45k—~3.1kAutomated safety check: PassApache-2.0
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0
Pull Request Title and Body Writeropeninterpreter/openinterpreter69k2 repos~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    297k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed
  • Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed
  • Open Code Review CLI

    alibaba/open-code-review

    Runs the ocr command-line tool to review Git changes, a commit or a branch comparison with an AI model, returning line-level comments and optionally applying fixes.

    45k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed
  • Pull Request Title and Body Writer

    openinterpreter/openinterpreter

    Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.

    69k GitHub starsUsed in 2 repos~1.1k tokens
    DevelopmentAuto-check passed
  • Understand Diff Analysis

    Egonex-AI/Understand-Anything

    Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.

    86k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check passed

More from OutThisLife/brooklyn-skills

All 22 skills in this repo
  • Draft Tweet

    OutThisLife/brooklyn-skills

    Draft X/Twitter posts about shipped work. An agent skill from OutThisLife/brooklyn-skills.

    199 GitHub stars~456 tokensUpdated 3 days ago
    Auto-check passed
  • Free Disk Space

    OutThisLife/brooklyn-skills

    Safely reclaim disk space on macOS without touching personal or agent data.

    199 GitHub stars~433 tokensUpdated 3 days ago
    Auto-check passed
  • List Open Work

    OutThisLife/brooklyn-skills

    List my open MRs/PRs in the current repo/worktree, each with its tracker ticket.

    199 GitHub stars~1.5k tokensUpdated 3 days ago
    Auto-check passed
  • PR Ready

    OutThisLife/brooklyn-skills

    Clear everything blocking an existing PR/MR from merging — rebase onto the default branch, get CI green, and resolve review threads (Copilot and human).

    199 GitHub stars~2.5k tokensUpdated 3 days ago
    Auto-check passed
  • PR Triage

    OutThisLife/brooklyn-skills

    Maintainer triage on OTHER people's PRs/MRs — verdict of approve, supersede, or close, salvage with credit, close the cluster.

    199 GitHub stars~4.7k tokensUpdated 3 days ago
    Auto-check passed
  • Work

    OutThisLife/brooklyn-skills

    Kick off a task in a fresh isolated git worktree instead of the current checkout.

    199 GitHub stars~858 tokensUpdated 3 days ago
    Auto-check passed

Works with

Categories

Questions about PR Update

What does PR Update do?

Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff. PR Update is an agent skill from OutThisLife/brooklyn-skills. Open a PR/MR if missing, or refresh an existing one's title and description so they match the current diff.

When should I use PR Update?

PR Update fits situations like: the user says /pr-update; refresh the PR title/description; wants the PR opener/manager flow.

How do I install PR Update in Claude Code?

Run `npx skills add OutThisLife/brooklyn-skills --skill pr-update -a claude-code`. Or copy the skill folder (skills/pr-update in OutThisLife/brooklyn-skills) into .claude/skills/pr-update in your project. Claude Code loads it when a task matches its description.

How do I install PR Update in Codex?

Run `npx skills add OutThisLife/brooklyn-skills --skill pr-update -a codex`. Or copy the skill folder (skills/pr-update in OutThisLife/brooklyn-skills) into .agents/skills/pr-update in your project. Codex loads it when a task matches its description.

Can I use PR Update in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add OutThisLife/brooklyn-skills --skill pr-update -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pr-update, .gemini/skills/pr-update, .github/skills/pr-update and .opencode/skills/pr-update in your project.

What does PR Update need to run?

Going by SKILL.md and its folder, PR Update needs the command-line tools its instructions call (git, gh, glab and jq).

Does PR Update access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is PR Update safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does PR Update use?

PR Update is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does PR Update use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to PR Update?

Skills that share tags, products or a category with PR Update: Finishing a Development Branch (obra/superpowers, 297k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Open Code Review CLI (alibaba/open-code-review, 45k stars) and Create Pull Request (cline/cline, 70k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains PR Update?

OutThisLife (a GitHub user) maintains it in OutThisLife/brooklyn-skills, which has 199 GitHub stars. The repository holds 22 skills in this directory. The repository was last updated on October 5, 2026.

Source: OutThisLife/brooklyn-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.