Agent skill

Update PR

by remix-run in remix-run/remix

Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now.

MITAuto-check passedDevelopment

Install Update PR

skills CLI
$ npx skills add remix-run/remix --skill update-pr -a claude-code

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

GitHub CLI
$ gh skill install remix-run/remix update-pr --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/remix-run/remix.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/update-pr .claude/skills/update-pr && 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
update-pr
GitHub stars
33k
Token cost
~651 tokens
SKILL.md length
358 words
Files
2
Skills in repo
19
Repo updated
First seen
Licence
MIT

At a glance

Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now.

  • Works in 5 steps: Read the current PR title/body and the… → Identify the PR's current net-new scope,… → Rewrite the body from scratch so it… → …
  • The user asks to update
  • SKILL.md covers Overview, Workflow, Rules and Applying The Update
  • Calls gh

What it does

Update PR is an agent skill from remix-run/remix. Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now. Use when the user asks to update, rewrite, refresh, fix, or tighten a PR title/body, or when the PR scope has changed and the metadata needs to be brought back in sync.

Its SKILL.md is about 650 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Development, covering Pull requests. It works with GitHub. The repository describes itself as: The fully-stacked web framework. The licence is MIT.

When your agent uses it

  • The user asks to update
  • Tighten a PR title/body
  • The PR scope has changed and the metadata needs to be brought back in sync

Example prompts

  • “/update-pr”

Workflow steps

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

  1. Read the current PR title/body and the current branch diff before drafting.
  2. Identify the PR's current net-new scope, APIs, behavior changes, and reviewer-relevant context.
  3. Rewrite the body from scratch so it describes the shipped feature/fix as it exists now.
  4. Review the title at the same time and update it whenever the body is updated.
  5. Apply the update with gh pr edit.

What it can do on your machine

Read from SKILL.md and the folder at commit 27bd7a4. 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:

    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.

    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

Update PR loads about 651 tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 358 words of instructions outside code blocks.

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

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 passed

The automated check found no risky patterns in SKILL.md.

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 remix-run/remix at commit 27bd7a4, republished under its MIT licence (© remix-run). 358 words, ~651 tokens.

Download SKILL.mdSave it as .claude/skills/update-pr/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
update-pr
description
Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now. Use when the user asks to update, rewrite, refresh, fix, or tighten a PR title/body, or when the PR scope has changed and the metadata needs to be brought back in sync.

Update PR

Overview

Rewrite pull request metadata as if drafting it from scratch for the current diff. Treat the title and body as a current reviewer-facing summary of the final net-new feature or bug fix in the PR, not as commentary about prior versions of the PR or the path taken to get there.

Workflow

  1. Read the current PR title/body and the current branch diff before drafting.
  2. Identify the PR's current net-new scope, APIs, behavior changes, and reviewer-relevant context.
  3. Rewrite the body from scratch so it describes the shipped feature/fix as it exists now.
  4. Review the title at the same time and update it whenever the body is updated.
  5. Apply the update with gh pr edit.

Rules

  • Never write the description as an update to itself. Do not say things like "this expands the original PR", "this PR now also", or similar process narration unless the user explicitly wants history called out.
  • Describe the net-new feature or bug fix, not the implementation journey. Do not call out intermediate cleanup, refactors, rewrites, or iteration details unless they are necessary to understand the final delivered behavior.
  • Always evaluate the title when updating a PR. If the scope or emphasis changed, rewrite the title too.
  • Write in terms of the present PR contents, using concise reviewer-facing language.
  • For feature PRs, focus the summary on what Remix gains: new packages, public APIs, behaviors, integrations, and documentation. Do not spend bullets on test additions, cleanup work, or internal restructuring unless those are themselves a meaningful part of the shipped feature.
  • For bug-fix PRs, focus the summary on the bug, the fix, and any user-visible behavior change. Do not narrate the debugging process or incidental refactors.
  • Keep the structure minimal: one short introductory paragraph plus flat bullets is usually enough.
  • Include usage examples when the PR introduces or materially changes a feature API.
  • Preserve still-relevant issue links or context, but drop stale framing.
Show full SKILL.md (36 more words)Show less

Applying The Update

  • Draft the new title and body in a temporary file.
  • Use gh pr edit <number> --title "<title>" --body-file <file>.
  • Re-read the PR after editing to confirm the final title/body match the intended framing.

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

Files

SKILL.md and 1 other file in .agents/skills/update-pr of remix-run/remix.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 27bd7a4

Compare with similar skills

Update PR 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.

Update PR compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Update PR this skillremix-run/remix33k—~651Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Check PRonyx-dot-app/onyx32k2 repos~2.3kAutomated safety check: PassMIT
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
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

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed
  • Check PR

    onyx-dot-app/onyx

    Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.

    32k GitHub starsUsed in 2 repos~2.3k 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
  • 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
  • Official

    Runs a loop on a GitHub pull request: fetch review state, triage comments into actions, implement them and resolve threads, repeating until nothing actionable is left.

    48k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

More from remix-run/remix

All 19 skills in this repo
  • Supersede PR

    remix-run/remix

    Safely replace one GitHub pull request with another. An agent skill from remix-run/remix.

    33k GitHub stars~456 tokensUpdated yesterday
    Auto-check passed
  • Add Package

    remix-run/remix

    Create or align a package in the Remix monorepo to match existing package conventions.

    33k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed
  • Author UI Primitives

    remix-run/remix

    Build idiomatic headless primitives in packages/ui for Remix.

    33k GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • Fix Issue

    remix-run/remix

    Fix a reported issue in Remix from a GitHub issue. An agent skill from remix-run/remix.

    33k GitHub stars~1.8k tokensUpdated yesterday
    Auto-check passed
  • Make Demo

    remix-run/remix

    Create or revise demos in the Remix repository. An agent skill from remix-run/remix.

    33k GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed
  • Make PR

    remix-run/remix

    Create GitHub pull requests with clear, reviewer-friendly descriptions.

    33k GitHub stars~847 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Update PR

What does Update PR do?

Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now. Update PR is an agent skill from remix-run/remix. Update an existing GitHub pull request title and description so they accurately describe the pull request as it exists now.

When should I use Update PR?

Update PR fits situations like: the user asks to update; tighten a PR title/body; the PR scope has changed and the metadata needs to be brought back in sync.

How do I install Update PR in Claude Code?

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

How do I install Update PR in Codex?

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

Can I use Update PR 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 remix-run/remix --skill update-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/update-pr, .gemini/skills/update-pr, .github/skills/update-pr and .opencode/skills/update-pr in your project.

What does Update PR need to run?

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

Does Update PR access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Update PR safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Update PR use?

Update PR 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 Update PR use?

About 651 tokens (SKILL.md is roughly 2.6k 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 Update PR?

Skills that share tags, products or a category with Update PR: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k 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 Update PR?

remix-run (a GitHub organization) maintains it in remix-run/remix, which has 33,396 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 6, 2026.

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