Cv Create Issue
Productivitycv-create-issueCv Create Issue is an Agent Skill for productivity published in the CurvineIO/curvine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Create a GitHub issue for Curvine using repository templates, with extended Goal/Not Goal/Test Plan sections for features. Use when user asks to create an issue, report a serious bug found during testing, or when agent should suggest filing an issue for the current problem.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/CurvineIO/curvine/blob/HEAD/.agents/skills/cv-create-issue/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cv-create-issue, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
cv-create-issue
Create structured GitHub issues that follow .github/ISSUE_TEMPLATE/ and Curvine conventions.
When to Use
- User explicitly asks to create / file / open an issue
- A serious bug is found during testing (data loss, crash, security, CI breakage)
- Agent detects an unresolved problem worth tracking — ask user whether to file an issue
Step 1: Classify
| Type | Template | Label | Title prefix |
|---|---|---|---|
| Bug | bug_report.md | bug | [BUG]: |
| Feature | feature_request.md | enhancement | [FEATURE] |
Search for duplicates first:
gh issue list --search "<keywords>" --state open --limit 10
Step 2: Draft Body
Bug (follow template)
Required sections from .github/ISSUE_TEMPLATE/bug_report.md:
- Describe the bug
- To Reproduce (numbered steps)
- Expected behavior
- OS Version (OS, Curvine version/branch, relevant config)
- Additional context (logs, screenshots)
Feature (template + extensions)
Base sections from .github/ISSUE_TEMPLATE/feature_request.md:
- Is your feature request related to a problem?
- Describe the solution you'd like
- Describe alternatives you've considered
- Additional context
Required extra sections for Feature issues:
# Goal
Design scope: list sub-requirements and the problem each solves.
| Sub-requirement | Problem solved |
| --------------- | -------------- |
| ... | ... |
# Not Goal
Modules, features, or boundaries this issue must **not** touch.
- ...
# Test Plan
| Test case | Test objective | Modules involved |
| --------- | -------------- | ---------------- |
| ... | ... | ... |
Step 3: Confirm with User
Show title + full body preview. Wait for approval before gh issue create.
Step 4: Create
# Bug
gh issue create \
--title "[BUG]: <summary>" \
--label bug \
--body "$(cat <<'EOF'
...
EOF
)"
# Feature
gh issue create \
--title "[FEATURE] <summary>" \
--label enhancement \
--body "$(cat <<'EOF'
...
EOF
)"
Step 5: Output
Return issue number, URL, and suggested next step:
- Bug fix → cv-handle-issue
- Large feature → cv-tasks-breakdown
Rules
- Body in English unless user requests otherwise
- One issue per topic
- For sub-tasks of a parent issue, prefix title with
[SUB]and linkParent: #<n>in body