用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/verl-project/verl --skill pr命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | pr |
| description | Create or update a pull request following verl project conventions. |
| user_invocable | true |
When the user asks to create or update a PR, follow these steps:
Read the following and understand the current branch's changes compared to main:
If a PR already exists for this branch, also read its current title, body, and review comments.
Follow the PR template strictly for both title format and body sections. Only check checklist boxes for steps that have actually been completed.
When updating, ensure the title and body still accurately reflect all changes on the branch, not just the latest commit.
Write the body as GitHub-flavored Markdown, not fixed-width plain text. Keep each paragraph and each list item on a single logical line and separate blocks with blank lines. Do not hard-wrap running prose at a column limit: GitHub renders a single newline inside a paragraph or list item as a space, so a manually wrapped sentence turns into unintended mid-sentence breaks in the rendered PR. Watch two easy-to-miss cases: a wrapped line whose continuation starts with #<number> (e.g. an issue reference like #7060) reads as a heading in the source and is easy to leave split, and list-item continuations that are indented but should still join their item. Let the editor soft-wrap; only insert a newline to start a new paragraph, list item, table row, or fenced code block. Before submitting, re-read the body (or the round-tripped version fetched back from GitHub) and confirm no paragraph or list item is split across multiple source lines.
Run pre-commit and fix any issues before creating or pushing.
main by default unless the user specifies otherwise.Return the PR URL when done.
基于 SOC 职业分类