Run any Skill in Manus with one click

update-pr

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.

Run Skill in Manus

Stars33,077

Forks2,775

UpdatedMarch 20, 2026 at 02:50

Source

remix-run

remix-run/remix

View GitHub Repository View Creator Repositories

Install command

Download

Run Skill in Manus

Useful forSOC

Software DevelopersComputer and Mathematical Occupations15-1252L4

File Explorer

2 files

SKILL.md

readonly

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

Read the current PR title/body and the current branch diff before drafting.
Identify the PR's current net-new scope, APIs, behavior changes, and reviewer-relevant context.
Rewrite the body from scratch so it describes the shipped feature/fix as it exists now.
Review the title at the same time and update it whenever the body is updated.
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.

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.

More from this repository

same repository

remix

remix-run/remix

Build and review Remix 3 applications using the `remix` npm package and subpath imports. Use when working on Remix app structure, routes, controllers, middleware, validation, data access, auth, sessions, file uploads, server setup, UI components, hydration, navigation, or tests.

2026-06-0233.1k

fix-issue

remix-run/remix

Fix a reported issue in Remix from a GitHub issue. Use when the user provides a GitHub issue URL and asks to fix a bug, investigate an issue, or reproduce a problem. Handles the full workflow: fetching the issue, finding the reproduction, writing a failing test, and implementing the fix.

2026-05-2933.1k

make-changes

remix-run/remix

Create or update Remix repo change files under `packages/*/.changes`. Use when a user asks for release notes, changes, a missing changelog entry, a prerelease note, or an update to existing unpublished release notes.

2026-05-2933.1k

make-pr

remix-run/remix

Create GitHub pull requests with clear, reviewer-friendly descriptions. Use when asked to open or prepare a PR, especially when the PR needs strong context, related links, and feature usage examples. This skill enforces concise PR structure, avoids redundant sections like validation/testing, and creates the PR with gh CLI.

2026-05-2933.1k

add-package

remix-run/remix

Create or align a package in the Remix monorepo to match existing package conventions. Use when adding a brand new package under packages/, or when fixing an existing package's structure, test setup, TypeScript/build config, code style, and README layout to match the rest of Remix 3.

2026-05-2233.1k

publish-placeholder-package

remix-run/remix

Publish a placeholder npm package at version 0.0.0 so package names are reserved and npm OIDC permissions can be configured before CI publishing. Use when creating a brand-new package that is not ready for full release.

2026-05-2233.1k

Update PR

Overview

Workflow

Read the current PR title/body and the current branch diff before drafting.

Identify the PR's current net-new scope, APIs, behavior changes, and reviewer-relevant context.

Rewrite the body from scratch so it describes the shipped feature/fix as it exists now.

Review the title at the same time and update it whenever the body is updated.

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.

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.