update-pr
Skill0 starsChanged 56 days agoMITView on GitHub
Update the pull request for the current session. Use when the user wants to push new changes to an existing PR.
14 other projects use a version of this.
Adopted by
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Most recently taken up by
- Trixx4191/asrartheir own version, first seen Nov 15, 2026
- frostney/pascal-mcp-sdktheir own version, first seen Oct 21, 2026
- raine/skillstheir own version, first seen Oct 21, 2026
- microsoft/vscodeword for word, first seen Oct 13, 2026
- frostney/known-good-routetheir own version, first seen Oct 11, 2026
- frostney/knipstheir own version, first seen Oct 9, 2026
Used with
Projects with it also use native-nostalgia-stack, software-engineering-excellence and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
frostneySkillnative-nostalgia-stack
Applies the user's FreePascal toolchain and its build, formatting, hook, and test contracts while leaving project-specific mechanics local. Use when scaffolding or working in a FreePascal project that follows this toolchain.
Also in 3 projects that use this
frostneySkillsoftware-engineering-excellence
Applies the user's engineering standards during substantial technical work: preserve scope, use current evidence, delegate independent parts, and complete authorized outcomes. Use during substantial implementation, debugging, refactoring, or multi-part delivery work.
Also in 3 projects that use this
withpiperSkillroadmap-review
Audit roadmap health — issues, dependency order, spec coverage, doc freshness. Use when speccing a new initiative. Use when /phase-plan output looks suspicious. Use before /roadmap-create reruns.
Also in 3 projects that use this
Model Context ProtocolSkillproject-structure
Where things live in the Inspector repo — which client owns which surface, what is in core/ versus clients/web, and what each top-level directory is for. Use when locating code, deciding where a new module belongs, or answering which package owns or contains a given area of the codebase.
Also in 3 projects that use this
ReinaMacCredySkillcodebase-audit
Deep codebase audit that first reads project docs (AGENTS.md, README.md) and investigates the architecture, then systematically finds hardcoded constants that should be dynamic and unfinished code (TODOs, "will"/"would" in comments). Use this skill when the user wants a thorough code review for hygiene issues, asks to find hardcoded values, wants to audit for TODOs or incomplete code, says things like "audit this codebase", "find hardcoded stuff", "what's unfinished", "find tech debt", "code hygiene check", or asks you to look across the whole project for issues. Also use when the user asks to understand a project before making changes, or wants a comprehensive health check of their codebase.
Also in 3 projects that use this
sahinSkillcreate-issue
Also in 3 projects that use this
Other versions14 projects use a version of this.
Word for word · 2
- microsoft/vscode★ 195k100% same
- patterson-agents/skills★ 0100% same
Edited · 0
None found.
Wrote their own version · 12
- remix-run/remix★ 33ksame name
- NVIDIA-NeMo/DataDesigner★ 2.4ksame name
- ReflexioAI/claude-smart★ 795same name
- ReflexioAI/reflexio★ 385same name
- frostney/pascal-mcp-sdk★ 2same name
- raine/skills★ 2same name
- Trixx4191/asrar★ 2same name
- zkmake/skills★ 2same name
- frostney/knips★ 1same name
- mitchdowd/skills★ 1same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository32 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- act-on-feedbackSkill
- algorithmic-artSkill
- animateSkill
- canvas-designSkill
- coderSkill
- code-reviewSkill
- coderSkill
- commitSkill
- create-draft-prSkill
- create-prSkill
- criticSkill
- designerSkill
- design-taste-frontendSkill
- fix-ciSkill
- frontend-designSkill
- generalistSkill
- generate-run-commandsSkill
- mergeSkill
- ponytailSkill
- researcherSkill
- researcherSkill
- securitySkill
- shadcnSkill
- syncSkill
- sync-upstreamSkill
- theme-factorySkill
- toolsSkill
- troubleshootSkill
- ui-ux-pro-maxSkill
- update-skillsSkill
- web-design-engineerSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Update the existing pull request for the current session.
- Distinctive: line 12
Check whether the pull request has any commits that are not yet present on the current branch (incoming changes).
- Distinctive: line 13
Run the compile and hygiene tasks (fixing any errors)
- Very specific: line 14
If there are any uncommitted changes, use the /commit skill to commit them
- Distinctive: line 15
If the outgoing changes introduce significant changes to the pull request, update the pull request title and description to reflect those …
- Distinctive: line 16
Update the pull request with the new commits and information
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- Customize this skill and select save to override its behavior. Delete that copy to restore the built-in behavior. -->Update Pull Request
Update the existing pull request for the current session. The context block appended to the prompt contains the pull request information.
- Check whether the pull request has any commits that are not yet present on the current branch (incoming changes). If there are any incoming changes, pull them into the current branch and resolve any merge conflicts
- Run the compile and hygiene tasks (fixing any errors)
- If there are any uncommitted changes, use the
/commitskill to commit them - If the outgoing changes introduce significant changes to the pull request, update the pull request title and description to reflect those changes
- Update the pull request with the new commits and information
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

