메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Perform 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.
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.
<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.
| name | cv-create-pr |
| description | 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. |
Create or update a PR with Curvine title and body conventions.
cv-handle-issue or task commits are ready to publishmake format
git status
git diff
Only stage files changed in the current task/session. Confirm with user before commit.
<type>(<module>): <description> (#<issueNumber>)
Example: feat(fuse): add new compression algorithm (#123)
Supported types: feat, fix, docs, style, refactor, perf, test, chore, ci, build, revert
Show title preview and get user approval.
git add <confirmed-files>
git commit -m "$(cat <<'EOF'
<type>(<module>): <subject>
<optional body>
EOF
)"
git push -u origin HEAD
All PR bodies in English. Use this structure:
# Summary
<1-3 sentences: what this PR does and why>
# Issue Describe / Design
Closes #<issueNumber> (or "Related to #<n>")
For **bug fixes**, include:
- Root cause
- Reproduction steps
- Fix approach
For **features**, include:
- Design decisions and trade-offs
- Link to parent issue / sub-issues if applicable
# Changes
| Module / File | Change | Impact on existing behavior |
| ------------- | ------ | --------------------------- |
| `path/to/file` | ... | None / behavior change: ... |
# Test verified
| Test case | Result | Notes |
| --------- | ------ | ----- |
| `cargo test -p ...` | PASS | |
| ... | | |
# Dependencies
- Related PRs: #<n> or None
- Related issues: #<n> or None
- Blocks / blocked by: or None
Do not include tool watermarks (e.g. "Made with Cursor").
Preview full title + body; wait for user approval.
gh pr create \
--title "<type>(<module>): <description> (#<issueNumber>)" \
--body "$(cat <<'EOF'
# Summary
...
EOF
)"
Default: draft unless user says ready:
gh pr create --draft --title "..." --body "..."
gh pr edit <number> \
--title "<type>(<module>): <description> (#<issueNumber>)" \
--body "$(cat <<'EOF'
...
EOF
)"
Or update current branch PR:
gh pr view --json number
gh pr edit <number> --title "..." --body "..."
make format passed