メニュー
Fix a Curvine GitHub issue from analysis through plan approval to implementation, routing large features to cv-tasks-breakdown. Use when user asks to fix, resolve, or implement a specific issue URL or issue number.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | cv-handle-issue |
| description | Fix a Curvine GitHub issue from analysis through plan approval to implementation, routing large features to cv-tasks-breakdown. Use when user asks to fix, resolve, or implement a specific issue URL or issue number. |
End-to-end issue resolution with explicit user approval before coding.
#<number>)gh auth status OKgh issue view <NUMBER> --json number,title,body,labels,state,url
Extract:
If issue is closed or scope is unclear, stop and ask user.
Summarize for the user:
| Item | Content |
|---|---|
| Type | bug / feature |
| Problem | What is wrong or what is requested |
| Affected modules | From issue body + codebase exploration |
| Risks | Breaking changes, concurrency, compatibility |
| Test strategy | Existing tests + new cases needed |
Use deepwiki / codegraph as needed for CurvineIO/curvine.
Present a plan:
## Proposed Approach
1. ...
2. ...
## Files to touch (estimate)
- `path/...` — ...
## Test plan
- ...
## Estimated size
~<N> lines / <M> files
| Estimate | Next step |
|---|---|
| ≤ ~500 lines | Continue with this skill after user approval |
| > ~500 lines or multi-module feature | Use cv-tasks-breakdown; create sub-issues |
Do not write code until the user explicitly approves the plan.
Iterate on the plan until approval. For ambiguous requirements, ask clarifying questions.
After approval:
git fetch origin
git checkout main && git pull origin main
git checkout -b fix/<NUMBER>-<short-slug> # or feat/...
.cursor/rules/std-common/ai-workflow.mdcmake format and relevant tests before commitIf using task breakdown, complete one task / one commit at a time.
When implementation and tests pass, use cv-create-pr:
<type>(<module>): <description> (#<NUMBER>)cv-tasks-breakdownPerform a direct code review of a Curvine PR by reading the diff and changed files, analyzing correctness, safety, and design issues, and producing structured findings. Use when user asks to review a PR's code, do a code review, or check a PR before merge.
Add or update Curvine cv-* project skills under .agents/skills/, following naming and layout conventions, and sync the AGENTS.md registry. Use when creating a new cv skill, updating an existing cv skill structure, or registering skills after changes.
Review an existing Curvine PR, analyze review comments one by one with an accept/reject table, fix after user approval, update the PR, reply to comments, and resolve threads. Use when user asks to review a PR, handle review comments, or provides a PR URL.
Create or update a Curvine pull request with standardized title and body sections (Summary, Issue/Design, Changes table, Test verified, Dependencies). Use when user asks to create, submit, update, or push a PR.
<One sentence: what this skill does>. Use when <comma-separated triggers>.
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.