remix-run/update-pr
.agents/skills/update-pr/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add remix-run/remix update-prInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 11, 2026, 10:36 PM31.7s2 files scanned
SKILL.md
- 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.
Related Skills
remix-run/remix-ui
tools
VerifiedTrustedCommunity
Build the UI of a Remix app. Use when creating pages, layouts, client entries, interactions, stateful UI, navigation, hydration, styling, animations, reusable mixins, or UI tests.
32,605SKILL.mdUpdated Apr 11, 2026
remix-run/remix-project-layout
development
VerifiedTrustedCommunity
Describe the ideal layout of a Remix application, including canonical directories, route ownership, naming conventions, and file locations on disk. When asked to bootstrap that layout in a new directory, run the bundled TypeScript script.
32,605SKILL.mdUpdated Apr 11, 2026
remix-run/write-readme
documentation
VerifiedTrustedCommunity
Write or rewrite package README files in the style used by the Remix repository. Use when drafting a new package README, revising an existing README, or reviewing README structure, examples, installation instructions, and section ordering for Remix packages.
32,605SKILL.mdUpdated Apr 11, 2026
remix-run/write-api-docs
development
VerifiedTrustedCommunity
Write or audit public API docs for Remix packages. Use when adding or tightening JSDoc on exported functions, classes, interfaces, type aliases, or option objects.
32,605SKILL.mdUpdated Apr 11, 2026