file-pr
Skill3 starsChanged 5 months agoApache-2.0View on GitHub
File or update a GitHub PR for a prepared branch when requested, including as part of takeover.
- Commits and pushes
24 other projects use a version of this.
Adopted by
Most recently taken up by
- lihbr/skillstheir own version, first seen Nov 15, 2026
- scottwater/skillstheir own version, first seen Nov 8, 2026
- salasebas/skillstheir own version, first seen Nov 8, 2026
- GeiserX/sstacktheir own version, first seen Nov 8, 2026
- ShlomiPorush/agent-skillstheir own version, first seen Nov 3, 2026
- shubrt/skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use docs-loop, full-loop 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.
GeiserXSkilldocs-loop
Use when the user asks to audit docs, check documentation for stale claims, or verify docs against the code.
Also in 3 projects that use this
GeiserXSkillfull-loop
Drive a repository to done with sergio-loop, then keep improving it with refine-loop at a descending theta. Use only when the user explicitly invokes full-loop.
Also in 3 projects that use this
- +7 more from GeiserX
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- t3dotgg/tstack★ 3.8ksame name
- assisjp/specflow★ 17same name
- GeiserX/agent-skills★ 6same name
- GeiserX/sstack★ 6same name
- GeiserX/claude-skills★ 5same name
- itsyasirkhandev/skills★ 4same name
- Dhruv2mars/skills★ 3same name
- bhagyamudgal/skills★ 2same name
- connorch/skills★ 2same name
- falcondev-oss/skills★ 2same name
14 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 repository44 other files it gives its agents.
- skills/supabase-postgres-best-practices/AGENTS.mdAGENTS.md
- skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- skills/supabase-postgres-best-practices/CLAUDE.mdCLAUDE.md
- ai-app-security-auditSkill
- ai-slide-templatesSkill
- babysit-prSkill
- backlog-ready-specSkill
- check-compiler-errorsSkill
- clawpackerSkill
- councilSkill
- deslopSkill
- devex-reviewSkill
- fix-ciSkill
- fix-merge-conflictsSkill
- founder-office-hoursSkill
- full-sendSkill
- full-stopSkill
- get-cookiesSkill
- get-pr-commentsSkill
- gh-issue-priority-handoffSkill
- image2-with-codexSkill
- investigateSkill
- leaving-pr-commentsSkill
- local-ultra-reviewSkill
- modernizeSkill
- npm-release-pipelineSkill
- peer-reviewSkill
- plan-devex-reviewSkill
- planmode-ceoSkill
- planmode-engineerSkill
- qa-onlySkill
- review-and-shipSkill
- run-smoke-testsSkill
- security-best-practicesSkill
- site-design-auditSkill
- site-design-fixSkill
- slow-is-fastSkill
- sol-loopSkill
- supabase-postgres-best-practicesSkill
- takeoverSkill
- vercel-react-best-practicesSkill
- xianyu-api-client-skillSkill
- xianyu-automation-skillSkill
- xianyu-product-manager-skillSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
3
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 8
Use when publishing an already prepared change is part of the user's request.
- Distinctive: line 13
If the same head has an open PR against a different base, confirm which PR the user wants before opening another.
- Distinctive: line 15
Follow the repository's title and template conventions.
- Very specific: line 19
Create or update the PR with gh.
“Common” is measured: kept by at least 6 in 10 of the 24 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
File PR
Use when publishing an already prepared change is part of the user's request.
- Confirm the intended head repository, branch, and base, and inspect the branch diff. Push the prepared branch if needed and authorized. Find any open PR for that head and base and update it instead of creating a duplicate. If the same head has an open PR against a different base, confirm which PR the user wants before opening another.
- Follow the repository's title and template conventions. Start the body with the problem or previous behavior, then describe the change and summarize verification. Follow the user's request and repository conventions for draft status and model attribution. Use only verified model or host names.
- Create or update the PR with
gh. Ifgh pr createhits a GraphQL rate limit, check for the matching PR via REST before retrying. If it is absent, usegh api --method POST repos/<owner>/<repo>/pullswith the resolved head and base, title, draft status, and-F body=@<file>. - Return the PR URL to the caller.
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.

