Install the "create-pr" agent skill from https://github.com/ByteDance-Seed/VeOmni/tree/main/.agents/skills/create-pr into .claude/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add ByteDance-Seed/VeOmni --skill create-pr -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "create-pr" agent skill from https://github.com/ByteDance-Seed/VeOmni/tree/main/.agents/skills/create-pr into .agents/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add ByteDance-Seed/VeOmni --skill create-pr -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "create-pr" agent skill from https://github.com/ByteDance-Seed/VeOmni/tree/main/.agents/skills/create-pr into .cursor/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add ByteDance-Seed/VeOmni --skill create-pr -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "create-pr" agent skill from https://github.com/ByteDance-Seed/VeOmni/tree/main/.agents/skills/create-pr into .gemini/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add ByteDance-Seed/VeOmni --skill create-pr -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "create-pr" agent skill from https://github.com/ByteDance-Seed/VeOmni/tree/main/.agents/skills/create-pr into .github/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add ByteDance-Seed/VeOmni --skill create-pr -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "create-pr" agent skill from https://github.com/ByteDance-Seed/VeOmni/tree/main/.agents/skills/create-pr into .opencode/skills/create-pr/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-pr", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
create-pr
GitHub stars
2.2k
Token cost
~1.6k tokens
SKILL.md length
722 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0
At a glance
Create a pull request for the current branch. An agent skill from ByteDance-Seed/VeOmni.
Works in 4 steps: Pre-flight Checks → Analyze Changes (automatic) → Generate Draft File and Push (automatic) → …
Tasks that involve Pull requests
SKILL.md covers Interaction Principle, Steps and Common Pitfalls
Calls git, make and gh
What it does
Create PR is an agent skill from ByteDance-Seed/VeOmni. Create a pull request for the current branch. Handles uncommitted changes, generates a PR title matching the [{modules}] {type}: {description} format enforced by CI, and fills in the PR description template. Trigger: 'create pr', 'open pr', 'submit pr', 'make pr'.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Pull requests. The repository describes itself as: VeOmni: Scaling Any Modality Model Training with Model-Centric Distributed Recipe Zoo. The licence is Apache-2.0.
When your agent uses it
Tasks that involve Pull requests
Example prompts
“create pr”
“open pr”
“submit pr”
“/create-pr”
Requirements
Docker
Workflow steps
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 16c94aa. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
make
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Create PR loads about 1.6k tokens when it runs. Until then it costs about 69 tokens; SKILL.md has 722 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~69
When it runs· the whole SKILL.md, loaded when a task matches
~1.6k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
NoteMentions a .env fileSKILL.md:30
ke quality`, stage relevant files (skip `.env`, credentials, large binaries), commit.
NoteMentions a .env fileSKILL.md:165
sitive files** before committing — skip `.env`, credentials, large binaries and warn the user.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
Download SKILL.mdSave it as .claude/skills/create-pr/SKILL.md (or your agent's skills folder).
name
create-pr
description
Create a pull request for the current branch. Handles uncommitted changes, generates a PR title matching the `[{modules}] {type}: {description}` format enforced by CI, and fills in the PR description template. Trigger: 'create pr', 'open pr', 'submit pr', 'make pr'.
Interaction Principle
Minimize confirmations. The only user confirmation is for uncommitted changes (Step 1.3). Everything after that — drafting, writing file, pushing, creating PR — runs automatically. Tool-level permission prompts (file write, git push) serve as implicit confirmation; do not add extra "are you sure?" pauses on top.
Steps
Step 1: Pre-flight Checks
Identify current branch:
bash
git branch --show-current
If on main — stop and ask the user to create a feature branch first.
Determine base branch: use main unless the user specifies otherwise.
Check for uncommitted changes (only confirmation point):
bash
git status
git diff --stat
If there are staged or unstaged changes, show a summary and ask the user:
"There are uncommitted changes. Commit them before creating the PR?"
If yes: run make quality, stage relevant files (skip .env, credentials, large binaries), commit.
If no: proceed with what's already committed.
If make quality fails: stop and report errors.
Check for existing PR on this branch:
bash
gh pr view --json number,title,body 2>/dev/null
Note the PR number if one exists.
Check commits ahead of base:
bash
git log origin/main..HEAD --oneline
If the branch has no commits ahead of main, stop — nothing to open a PR for.
Step 2: Analyze Changes (automatic)
Collect the full diff against the base branch:
bash
git diff main...HEAD
git log main..HEAD --oneline
Identify affected modules by mapping changed file paths to allowed module names:
Path prefix
Module
veomni/models/
model
veomni/trainer/
trainer
veomni/data/
data
veomni/distributed/
dist (use parallel when the change is about a parallelism strategy rather than the plumbing)
veomni/ops/
ops
veomni/checkpoint/
ckpt
veomni/optim/
optim
veomni/lora/
lora
configs/
config
docs/
docs
tests/, .github/workflows/
ci
docker/
docker
tasks/
task
.agents/
agent
anything with a measurable speed/memory claim
add perf
other / mixed
misc
omni, logging and release have no directory of their own — use them
for omni-model, log/telemetry-surface and release-plumbing changes
respectively.
The authoritative module and type lists live in
.github/workflows/check_pr_title.yml (allowedModules / allowedTypes).
Read it rather than trusting this table if a name is rejected.
Determine change type:
Type
When
feat
New functionality or capability
fix
Bug fix
refactor
Same behavior, better structure
chore
Maintenance, cleanup, config changes
test
Test-only changes
Show full SKILL.md (414 more words)Show less
Step 3: Generate Draft File and Push (automatic)
Apply /veomni-review before pushing. Use its applicability rules for
<base>...HEAD, including the documentation self-check and the narrowly
defined exemption for clean, exact reverts or approved-diff reapplications.
Partial reverts, extra edits and conflict resolutions need the normal gate.
Review again before a substantive update to an open PR. A risky verdict
stops the PR: report it and wait for the user.
Draft PR title in [{modules}] {type}: {description} format:
Multiple modules separated by comma: [model, data] feat: ...
Description: concise, lowercase start, no period, under 60 chars
Breaking changes: prepend [BREAKING]
Must pass the regex in .github/workflows/check_pr_title.yml
Draft the PR description by reading .github/PULL_REQUEST_TEMPLATE.md
and filling in its sections. Do not reproduce the template from memory — it
changes, and a stale copy silently drops checklist items.
New PR: .pr-drafts/<branch-name>.md — renamed to PR# after creation.
File format — first line is the PR title, blank line, then the description body:
markdown
[model] feat: add support for Qwen4
<sections copied from .github/PULL_REQUEST_TEMPLATE.md, filled in>
Keep the template's own bullet/checkbox style. Fill every section: an empty
### Test section is the most common review blocker. If the PR adds an
extension point (a mixin, hook or callback other modules must implement),
name its docs/ page under Design & Code Changes; with no such page,
write it first (see "Documenting an extension point" in /veomni-develop)
rather than claiming "Added/updated documentation".
Tell the user the draft file path (so they know where to find it if they want to review later).
Step 4: Push and Create/Update PR (automatic, immediately after Step 3)
Push the branch:
bash
git push -u origin HEAD
Create or update:
New PR (use --body-file to avoid shell escaping issues):bash
# Extract body from draft file (everything after the first blank line)
tail -n +3 .pr-drafts/<branch-name>.md > /tmp/pr-body.md
gh pr create --base <base-branch> --title "<title>" --body-file /tmp/pr-body.md
After creation, rename the draft file from <branch-name>.md to <pr-number>.md.
Create PR next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.
Checks a GitHub, GitLab, or Perforce (p4) pull request (or merge request, or shelved changelist) for unresolved review comments, failing status checks, and incomplete PR descriptions.
For a non-trivial pull request, write a self-contained HTML design doc under the temporary .pr/ directory and link a visibility-appropriate preview in the PR description, so maintainers grasp the…
Reviews WooCommerce code changes against the project's standards, flagging backend PHP architecture, naming, documentation, data integrity and testing violations.
A skill your agent uses for ANY bug, error, crash, wrong output, loss divergence, gradient explosion, test failure, CUDA error, distributed training hang, checkpoint load failure, or unexpected…
Create a pull request for the current branch. An agent skill from ByteDance-Seed/VeOmni. Create PR is an agent skill from ByteDance-Seed/VeOmni. Create a pull request for the current branch.
When should I use Create PR?
Create PR fits situations like: tasks that involve Pull requests.
How do I install Create PR in Claude Code?
Run `npx skills add ByteDance-Seed/VeOmni --skill create-pr -a claude-code`. Or copy the skill folder (.agents/skills/create-pr in ByteDance-Seed/VeOmni) into .claude/skills/create-pr in your project. Claude Code loads it when a task matches its description.
How do I install Create PR in Codex?
Run `npx skills add ByteDance-Seed/VeOmni --skill create-pr -a codex`. Or copy the skill folder (.agents/skills/create-pr in ByteDance-Seed/VeOmni) into .agents/skills/create-pr in your project. Codex loads it when a task matches its description.
Can I use Create PR in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ByteDance-Seed/VeOmni --skill create-pr -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-pr, .gemini/skills/create-pr, .github/skills/create-pr and .opencode/skills/create-pr in your project.
What does Create PR need to run?
Going by SKILL.md and its folder, Create PR needs the command-line tools its instructions call (git, make and gh). Our summary lists: Docker.
Does Create PR access the network?
SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Create PR safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Create PR use?
Create PR is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Create PR use?
About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Create PR?
Skills that share tags, products or a category with Create PR: Finishing a Development Branch (obra/superpowers, 297k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars), Check PR (onyx-dot-app/onyx, 32k stars) and PR Design Doc (OpenHands/OpenHands, 90k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create PR?
ByteDance-Seed (a GitHub organization) maintains it in ByteDance-Seed/VeOmni, which has 2,235 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 9, 2026.
Source: ByteDance-Seed/VeOmni on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
