open-pr
Skill15 starsChanged 2 months agoMITView on GitHub
Redacta un pull request para la rama actual rellenando la plantilla de PR del repositorio en función de los cambios de la rama. Úsalo cuando la persona pida abrir/crear un PR, preparar un pull request o escribir la descripción de un PR (p. ej. "abre un PR", "redacta el pull request de esta rama"). No hace merge.
- Commits and pushes
67 other projects use a version of this.
Adopted by
Most recently taken up by
- gmunaro/claude-skillstheir own version, first seen Nov 16, 2026
- mazzsva/claude-skillstheir own version, first seen Nov 16, 2026
- skillberry-ai/cap-evolvetheir own version, first seen Nov 15, 2026
- eduardokairalla1/personal-skillstheir own version, first seen Nov 15, 2026
- lucasalencar/skillstheir own version, first seen Nov 15, 2026
- jameswyse/skillstheir own version, first seen Nov 15, 2026
Used with
Projects with it also use implement-change, review-change and 8 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.
Codagent-AISkillimplement-change
Implements an approved change in one continuous session, with tiered test runs. Use when asked to implement a change from its approved definition, or to invoke codagent:implement-change.
Also in 3 projects that use this
thlaureSkillreview-change
Use this skill when the user asks for a code review, a correctness pass, a check before PR, or asks whether a Signalist change follows project conventions.
Also in 4 projects that use this
DataCoveySkillcommit-push
Commit and push the changes made on this chat session to the current branch. Use best practices from Conventional Commits.
Also in 3 projects that use this
saffron-healthSkilladdress-review
Address PR review comments systematically. Use when responding to code review feedback on a pull request.
Also in 3 projects that use this
AnthropicSkillwrite-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
Also in 3 projects that use this
owidSkillbabysit-pr
Spawn a background agent that babysits an open PR — triggers a Codex review, watches CI, judges and fixes valid findings, replies to and resolves review threads, and loops to a cap. Never merges. Trigger when the user asks to "babysit the PR", "ask for codex review(s) and watch CI", or after pushing a substantial chunk to a PR branch.
Also in 4 projects that use this
Other versions67 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 67
- Significant-Gravitas/AutoGPT★ 188ksame name
- storybookjs/storybook★ 92ksame name
- pascalorg/editor★ 26ksame name
- dask/dask★ 14ksame name
- polarsource/polar★ 10ksame name
- cloudflare/agents★ 6ksame name
- Kiln-AI/Kiln★ 5.3ksame name
- analogjs/analog★ 3.2ksame name
- raine/workmux★ 3ksame name
- Akylas/OSS-DocumentScanner★ 2.7ksame name
57 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 repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-auditSkill
- actualizar-plantillaSkill
- changelogSkill
- commitSkill
- configurar-repoSkill
- copywritingSkill
- design-system-auditSkill
- i18n-paritySkill
- identidadSkill
- instanciarSkill
- migration-guardSkill
- new-adrSkill
- new-specSkill
- open-issueSkill
- portar-cambioSkill
- prototipoSkill
- releaseSkill
- seo-auditSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 34
NO hagas merge, NO apruebes, y NO marques ítems de la lista de verificación que no estén realmente hechos.
“Common” is measured: kept by at least 6 in 10 of the 66 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
Prepara un pull request para la rama actual.
Antes de redactar nada, deja el cambio listo. Es el único momento en que alguien mira el conjunto completo, y lo que no se actualice aquí no se actualiza nunca:
- Corre el subagente
doc-keepersobre el diff: sincronizadocs/architecture/*, los diagramas (entidades, pantallas, auth, componentes), el ADR si hubo decisión, la entrada delCHANGELOG.mdy el ítem del roadmap que la spec declaró. - Corre
bash .githooks/pre-push: los siete checks del CI, en unos quince segundos y sin gastar minutos de Actions. - Repasa
docs/conventions/definition-of-done.md, y en especial lo que ninguna máquina comprueba: revisión humana del esquema, autorización probada con otro rol, los cuatro estados de la UI.
Si algo queda en rojo, no abras el PR: dilo y arréglalo primero. Un PR que nace rojo se normaliza y deja de mirarse.
- Corre el subagente
- Lee
.github/PULL_REQUEST_TEMPLATE.mdpara conocer las secciones requeridas y la lista de verificación. - Reúne contexto sobre los cambios de la rama:
git log <base>..HEAD --onelinepara la lista de commits (la base suele sermain).git diff <base>...HEAD --staty revisa los diffs relevantes.
- Rellena cada sección de la plantilla usando ese contexto:
- Resumen de qué cambió y por qué.
- Issues vinculados / ADRs o especificaciones relacionados si se mencionan.
- Notas de pruebas (qué ejecutaste o qué debería revisar quien haga la revisión).
- Marca los ítems de la lista de verificación que realmente apliquen; deja el resto para la persona autora.
- Crea el PR con la CLI
gh(p. ej.gh pr create --title ... --body ...) si la rama está pusheada; de lo contrario, muestra la plantilla rellenada para que la persona la pegue. - Informa la URL del PR o el cuerpo redactado.
NO hagas merge, NO apruebes, y NO marques ítems de la lista de verificación que no estén realmente hechos. Escribe un PR en borrador si el trabajo está incompleto.
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.

