# Cuga New Feature

> Create a new issue (upstream)

- Skill: `cuga-project/cuga-new-feature` (Agent Skill)
- Install (CLI): `npx skillmds@latest add cuga-project/cuga-new-feature`
- Raw SKILL.md: https://api.skillmd.com/api/skills/cuga-project/cuga-new-feature/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: cuga-project (https://skillmd.com/u/cuga-project)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/cuga-project/cuga-new-feature

---


# Create a new issue (upstream)

1. Create the issue with the GitHub CLI (`gh issue create`).
2. Open it against the **origin** upstream (use that remote / repository—not a fork-only default).
3. Labels: run `gh label list` for that upstream repository. Only use names that appear in that output. Always pass `--label needs-triage` and add other applicable labels. Do not invent label names.
4. Choose the correct title prefix based on the issue type:

   | Prefix | When to use |
   |---|---|
   | `[Feature]` | New functionality or capability |
   | `[Design]` | Architecture, API design, or UX proposal before implementation |
   | `[Refactor]` | Internal restructuring with no behavior change |
   | `[Performance]` | Speed, memory, or efficiency improvements |
   | `[Security]` | Vulnerability, safety concern, or hardening |
   | `[Docs]` | Documentation additions or corrections |
   | `[Test]` | Missing tests, flaky tests, or test infrastructure |
   | `[Chore]` | Dependency updates, cleanup, or tooling |
   | `[Epic]` | Large body of work grouping multiple issues |
   | `[Question]` | Clarification needed, not a task |

5. Write the body using the same sections as `.github/ISSUE_TEMPLATE/feature_request.yml`: What you want and why, How it could work, Links or extra context (if any). Incorporate the user's message and any selected editor/context so the issue is concrete and complete.
6. Do not add "Made with Cursor" or similar promotional footers to the issue.