update-pr
Commits relevant changes, merges the remote base when needed, pushes the current pull-request branch, and refreshes stale PR metadata. Use when asked to update or push changes to an existing pull request, or when the user runs /update-pr.
How do I install this agent skill?
npx skills add https://github.com/frostney/known-good-route --skill update-prIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill processes untrusted data from GitHub pull requests (titles, bodies, and diffs) and project templates while possessing the capability to execute git commands and invoke other high-authority skills. This creates a potential surface for indirect prompt injection.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
Update PR
Update the established PR through integration, relevant commits, a normal push
and current metadata. The request includes resolving routine conflicts and
running the declared PR gate; merging belongs to /deliver under the
delivery settings. Reuse the selected target
and prior authorization. Ask only when the intended PR, a
material
conflict-resolution choice or another material choice within this update
remains unclear.
When the current PR belongs to a native GitHub stack, read ../git-workflow/references/github-stacks.md. When PR media no longer shows the current behavior, or the change needs new media, refresh the affected parts using ../create-pr/references/walkthroughs.md; reuse media that still shows the current behavior. Media tooling gaps alone do not block the update.
- Apply
git-workflow. Inspect the current PR and its base branch, the branch, relevant local changes, recent commits and the fetched remote base asgit-workflowdefines it. Resolve a branch that needs the base under step 3 before deciding whether missing CI needs any action. - Stop if on the base branch or no open PR exists; report the required next
workflow. Stop likewise when
git-workflowgives the PR no remote base. - Merge the remote base into an ordinary branch only when
git-workflow's up-to-date rule calls for it. A branch that is behind keeps its head and its checks, including when this update commits new changes. Preserve both sides' required behavior in additive conflicts; regenerate generated files using the project's tool. Continue through validation when the resolution is established. For a verified native stack, capture remote heads and use the guardedgh stack syncor narrower official stack operation; never use raw rebase or force-push commands. - Apply
/code-review fix-alland/test-against-spec fixto the changed behavior, including any baseline integration. Reuse only evidence whose content, command, environment and coverage still match; a baseline merge or edit invalidates the checks it affects. Run missing or invalidated checks. Repair every verified in-scope requirement gap through/implement's development loop, then establish the declared PR gate. A preview needed to test an unpublished fix permits its draft update; resume testing on that exact revision before claiming readiness. - When relevant changes exist, commit them under
git-workflow: stage only those files, use a concise Conventional Commit subject, and never amend or skip hooks. Run the publication guard at each commit, push and PR write. - When the branch has commits its remote lacks, push an ordinary branch normally, setting upstream when needed. Push a verified stack only through the guarded official stack workflow.
- Reconcile the PR title and body with the complete current diff, scope and
linked issues. A push always changes the head, so after a push reconcile
the body again even when the summary still holds. Keep the title a Conventional Commit
subject for the whole change; it becomes the squash-merge commit subject, so
widened scope may also change its type. Follow
../agent-writing/references/pr-descriptions.md,
preserving explicit project-template requirements and replacing obsolete
summaries, intermediate development history and author verification
sections. Keep the
review note
at the end of the body, updated as it describes. Keep every PR template
heading verbatim and in order, and under a heading with nothing to say
write a one-line
Noneor the reason. Runtemplate-checkon the draft with--kind pr --body FILEbefore writing it and on the live body with--pr Nafter, and fix every heading problem it reports. - Report the updated PR, any new commit, metadata changes, what the
publication guard rewrote and observed validation. Include stack position
and rewritten branches when applicable.
Distinguish passed local checks from pending current-head CI. A draft PR
stays draft until
delivery-waitobserves every required check green on the pushed head; only then may it be marked ready for review. Return the exact current head and next transition to the active publication or delivery caller; that caller continues through CI and feedback. Started directly, continue under the delivery settings; withentry-points: deliver, the pushed head goes on to/deliver, which awaits its CI and review and takes the PR to the configured endpoint (its default whenORCHESTRATION.mdsets none). Withstop, end with this report. Report missing walkthrough requirements with remedies.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/frostney/known-good-route/update-pr">View update-pr on skillZs</a>