cuga-report-bug

# Report a bug (upstream issue)

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

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

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

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.