cuga-report-bug

# Report a bug (upstream issue)

Opciones de instalación

De forma predeterminada está seleccionado el prompt que primero revisa el origen. Puedes cambiar a un comando directo o descargar una copia local.

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Un comando directo omite el prompt de revisión. Revisa el origen antes de ejecutarlo.

npx skills add https://github.com/cuga-project/cuga-flo --skill cuga-report-bug

El comando permanece en una sola línea. Desplázate horizontalmente para revisarlo antes de copiarlo.

¿Prefieres una copia local? Descarga los archivos que SkillsMP tiene disponibles ahora.

Lee SKILL.md y los archivos complementarios que muestra SkillsMP antes de decidir si quieres instalarlo.

SKILL.md

Instrucciones de origen · Vista previa de solo lectura

name	cuga-report-bug
description	# Report a bug (upstream issue)
metadata	{"user-invocable":true,"disable-model-invocation":true}

Create the issue with the GitHub CLI (gh issue create).
Open it against the origin upstream (use that remote / repository—not a fork-only default).
Labels: run gh label list for that upstream repository (same scope as the issue, e.g. --repo owner/name if you are not using the default remote). Only use names that appear in that output. When you run gh issue create, pass --label bug and repeat --label <name> for each other applicable label. Do not invent label names.
Write the body using the same sections as .github/ISSUE_TEMPLATE/bug_report.yml: What happened, How to reproduce, Environment, Logs, screenshots, or config (if any). Incorporate the user’s message and any selected editor/context so the issue is concrete and reproducible.
Use a sensible title consistent with the template’s title prefix.
Do not add “Made with Cursor” or similar promotional footers to the issue.

1. Commit current changes, one per file or (depends what user asks), but if its build files then all build files one commit

### Step 1: Validate Your Local Repository do it all against upstream `origin`

# Create a new issue (upstream)

name	cuga-report-bug
description	# Report a bug (upstream issue)
metadata	{"user-invocable":true,"disable-model-invocation":true}

Create the issue with the GitHub CLI (gh issue create).
Open it against the origin upstream (use that remote / repository—not a fork-only default).
Labels: run gh label list for that upstream repository (same scope as the issue, e.g. --repo owner/name if you are not using the default remote). Only use names that appear in that output. When you run gh issue create, pass --label bug and repeat --label <name> for each other applicable label. Do not invent label names.
Write the body using the same sections as .github/ISSUE_TEMPLATE/bug_report.yml: What happened, How to reproduce, Environment, Logs, screenshots, or config (if any). Incorporate the user’s message and any selected editor/context so the issue is concrete and reproducible.
Use a sensible title consistent with the template’s title prefix.
Do not add “Made with Cursor” or similar promotional footers to the issue.