OpenParable
Skip to content
← Back to skills

Cv Create PR

Development
cv-create-pr

Cv Create PR is an Agent Skill for development published in the CurvineIO/curvine repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CurvineIO/curvine/blob/HEAD/.agents/skills/cv-create-pr/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cv-create-pr, 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-pr

Create or update a PR with Curvine title and body conventions.

When to Use

  • User asks to create / submit / open a PR
  • User asks to update PR title or body
  • After cv-handle-issue or task commits are ready to publish

Pre-flight

make format
git status
git diff

Only stage files changed in the current task/session. Confirm with user before commit.

PR Title Format

<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.

Commit Before PR

git add <confirmed-files>
git commit -m "$(cat <<'EOF'
<type>(<module>): <subject>

<optional body>
EOF
)"
git push -u origin HEAD

PR Body Template

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").

Create PR

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 "..."

Update Existing PR

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 "..."

Checklist

  • make format passed
  • Tests run and recorded in Test verified
  • Title matches format with issue number
  • Changes table covers key modules
  • User approved commit and PR content

Related