open-issue
Skill15 starsChanged 2 months agoMITView on GitHub
Redacta y crea un issue de GitHub rellenando la plantilla adecuada de .github/ISSUE_TEMPLATE/ según el tipo (bug, funcionalidad o tarea). Úsalo cuando la persona pida abrir/crear un issue, reportar un bug o registrar una tarea/petición (p. ej. "abre un issue por este bug", "crea un issue para la nueva funcionalidad", "registra esta tarea"). No cierra ni comenta issues existentes.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- agentdecksdk/agentdecktheir own version, first seen Sep 14, 2026
- brayandiazc/project-starter-template-en-aitheir own version, first seen Sep 7, 2026
- dlupiak/claude-session-dashboardtheir own version, first seen Mar 18, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- dlupiak/claude-session-dashboard★ 66same name
- agentdecksdk/agentdeck★ 4same name
- brayandiazc/project-starter-template-en-ai★ 2same name
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-prSkill
- portar-cambioSkill
- prototipoSkill
- releaseSkill
- seo-auditSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 33
NO inventes datos que no tengas (versiones, logs, entorno) — déjalos como indicaciones, NO crees un issue duplicado si ya existe uno igual …
- Very specific: line 34
NO crees un issue duplicado si ya existe uno igual (búscalo primero con gh issue list), y NO cierres, edites ni comentes issues existentes.
“Common” is measured: kept by at least 6 in 10 of the 3 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
Crea un issue bien formado usando la plantilla del repositorio.
- Mira las plantillas disponibles en
.github/ISSUE_TEMPLATE/y elige la que corresponda al tipo de issue:bug_report.md— un fallo o comportamiento incorrecto.feature_request.md— una nueva funcionalidad o mejora.task.md— una tarea de trabajo interna (chore, refactor, tooling). Si el tipo es ambiguo por lo que dice$ARGUMENTS, pregunta antes de elegir.
- Lee la plantilla elegida para conocer sus secciones requeridas y su encabezado
(
title:,labels:,assignees:). Respeta ese frontmatter. - Rellena cada sección con la información de
$ARGUMENTSy del contexto de la conversación:- Un título claro y en imperativo o descriptivo (no genérico como "bug").
- Pasos de reproducción / comportamiento esperado vs. actual para bugs.
- Motivación y criterios de aceptación para funcionalidades y tareas.
- Deja como indicación (no inventes) cualquier dato que no tengas: versiones, entorno, capturas.
- Crea el issue con la CLI
ghrespetando la plantilla, p. ej.gh issue create --title "…" --body "…" --label "…"(o--template <archivo>si se prefiere el flujo interactivo). Si no hay remoto configurado, muestra el issue relleno para que la persona lo pegue en GitHub. - Informa la URL del issue creado (o el cuerpo redactado).
Ejemplo: /open-issue el login falla con Google en Safari →
.github/ISSUE_TEMPLATE/bug_report.md relleno y publicado.
NO inventes datos que no tengas (versiones, logs, entorno) — déjalos como indicaciones,
NO crees un issue duplicado si ya existe uno igual (búscalo primero con gh issue list),
y NO cierres, edites ni comentes issues existentes.
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.

