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.