Create Cuda Python Pull Request
NVIDIA/cuda-python
Create a CUDA Python pull request from an approved personal or organization-owned fork, including the GitHub CLI GraphQL fallback for renamed organization-owned forks.
How to create a pull request for the intel/torch-xpu-ops repository.
Install Xpu Ops PR Creation
$ npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install intel/torch-xpu-ops xpu-ops-pr-creation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/xpu-ops-pr-creation .claude/skills/xpu-ops-pr-creation && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "xpu-ops-pr-creation" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creation into .claude/skills/xpu-ops-pr-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xpu-ops-pr-creation", 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.
$skill-installer install https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creationType 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.
$ npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install intel/torch-xpu-ops xpu-ops-pr-creation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/xpu-ops-pr-creation .agents/skills/xpu-ops-pr-creation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "xpu-ops-pr-creation" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creation into .agents/skills/xpu-ops-pr-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xpu-ops-pr-creation", 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.
$ npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install intel/torch-xpu-ops xpu-ops-pr-creation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/xpu-ops-pr-creation .cursor/skills/xpu-ops-pr-creation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "xpu-ops-pr-creation" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creation into .cursor/skills/xpu-ops-pr-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xpu-ops-pr-creation", 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.
$ gemini skills install https://github.com/intel/torch-xpu-ops.git --path .claude/skills/xpu-ops-pr-creation--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install intel/torch-xpu-ops xpu-ops-pr-creation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/xpu-ops-pr-creation .gemini/skills/xpu-ops-pr-creation && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "xpu-ops-pr-creation" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creation into .gemini/skills/xpu-ops-pr-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xpu-ops-pr-creation", 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.
$ gh skill install intel/torch-xpu-ops xpu-ops-pr-creationInstalls 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).
$ npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/xpu-ops-pr-creation .github/skills/xpu-ops-pr-creation && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "xpu-ops-pr-creation" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creation into .github/skills/xpu-ops-pr-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xpu-ops-pr-creation", 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.
$ npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install intel/torch-xpu-ops xpu-ops-pr-creation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/xpu-ops-pr-creation .opencode/skills/xpu-ops-pr-creation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "xpu-ops-pr-creation" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/xpu-ops-pr-creation into .opencode/skills/xpu-ops-pr-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "xpu-ops-pr-creation", 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
xpu-ops-pr-creation- GitHub stars
- 115
- Token cost
- ~1.2k tokens
- SKILL.md length
- 459 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
How to create a pull request for the intel/torch-xpu-ops repository.
- Works in 6 steps: Verify your branch → Write a reproducer test (mandatory) → Compose the PR body → …
- An agent has finished implementing a fix
- SKILL.md covers Step 1: Verify your branch, Step 2: Write a reproducer…, Step 3: Compose the PR body and Step 4: Run linting checks, plus 3 more sections
- Calls git and pytest
What it does
Xpu Ops PR Creation is an agent skill from intel/torch-xpu-ops, published by the product's own GitHub organization. How to create a pull request for the intel/torch-xpu-ops repository. Use when an agent has finished implementing a fix or feature and needs to prepare a branch and PR description that satisfies CI and review requirements.
Its SKILL.md is about 1.2k 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. It works with CUDA. The licence is Apache-2.0.
When your agent uses it
- An agent has finished implementing a fix
- Feature and needs to prepare a branch and PR description that satisfies CI and review requirements
Example prompts
- “/xpu-ops-pr-creation”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a033aa5. 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:
gitpytest
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Xpu Ops PR Creation loads about 1.2k tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 459 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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.
SKILL.md
The full file from intel/torch-xpu-ops at commit a033aa5, republished under its Apache-2.0 licence (© intel). 459 words, ~1,155 tokens.
Download SKILL.mdSave it as
.claude/skills/xpu-ops-pr-creation/SKILL.md (or your agent's skills folder).- name
- xpu-ops-pr-creation
- description
- How to create a pull request for the intel/torch-xpu-ops repository. Use when an agent has finished implementing a fix or feature and needs to prepare a branch and PR description that satisfies CI and review requirements.
- placeholders
- branch, title, description, test_line
PR Creation — torch-xpu-ops
- Read
.github/copilot-instructions.mdfor full repo context before starting. - Read
.claude/skills/fix-root-cause/SKILL.mdfor issue triaging before creating a PR.
MANDATORY STEPS:
- You MUST read the issue body "Root Cause Analysis" and "Proposed Fix Strategy" BEFORE proposing any fix.
- If there is a CUDA kernel implementation, you have to refer to it first.
- Before you make any changes, you need to understand the root cause, and answer yourself "why CUDA works but XPU failed". If there is any misalignment, you need to write in the PR body description.
- After you make changes, you need to answer "If the implementation is different with the CUDA logic, is it reasonable?" If there is any misalignment, you need to write in the PR body description.
Step 1: Verify your branch
git status # confirm clean working tree
git log main..HEAD --oneline # confirm commits are on your branch, not main
git diff main --stat # sanity-check the changed filesBranch must follow: agent/<slug> (lowercase, hyphens, max 50 chars).
Step 2: Write a reproducer test (mandatory)
Every PR must include a pytest-compatible test under test/repro/ if it is newly introduced. If the test is in PyTorch or torch-xpu-ops tests, you should explicitly write the run command in the PR body (see Step 3).:
Note: For now, if the test is in PyTorch, explicitly point it out in PR message with bold font!
- File name:
test_<description>.py - Contains
def test_...()functions orclass Test...classes - Runnable:
pytest test/repro/test_<description>.py - Imports
torch, targetsxpudevice (alsocudaif relevant)
Exceptions (CI-only changes, docs, build fixes): no new test file required, but you must name existing tests that validate the change.
Step 3: Compose the PR body
Use this exact template:
Fixes <original_issue_link>
<description of what the PR does and why>
Test: <one of the three forms below>Three valid Test: forms:
New reproducer added:
Test: test/repro/test_<description>.pyExisting test(s) cover it:
Test: test/repro/test_foo.py, test/xpu/test_bar_xpu.pyNo test applicable:
Test: none (<reason>)
The Test: line is required in every PR body. CI reviewers look for it.
Show full SKILL.md (175 more words)Show less
Step 4: Run linting checks
Before pushing, run pre-commit and/or lintrunner to catch style and lint issues:
# Option A — pre-commit (if configured)
pre-commit run --files $(git diff main --name-only)
# Option B — lintrunner (if configured)
lintrunner --take FLAKE8,MYPY,CLANGFORMAT -a $(git diff main --name-only)Fix any reported issues and amend your commit before proceeding. If neither tool is configured in the repo, skip this step and note it in your summary.
Step 5: Push your branch
git push origin agent/<slug>origin for this repo is intel/torch-xpu-ops. This is not a fork — push directly
to origin. Do not push to main.
Step 6: Open the PR (or hand off)
Agents do not auto-open PRs for this repo. Output your summary so a human can review and open the PR.
At the end of your response output EXACTLY this block:
### Agent Summary
- **What I found:** <one sentence>
- **What I changed:** <bullet list of files>
- **Test file:** test/repro/<filename>.py | none (<reason>)
- **Branch:** agent/<slug>
- **PR body draft:**
<title>
<description paragraph>
Test: <test line>
- **Open questions / risks:** <concerns or "None">Critical: The **Branch:** line must contain the exact branch name. It is machine-parsed.
Checklist before handing off
- pre-commit / lintrunner passed (or not configured — noted in summary)
-
src/, andtest/are consistent (if any were touched) - Test file added to
test/repro/orTest: none (reason)written - No unrelated files changed
- Commit message is imperative, max 72 chars
- Branch is
agent/<slug>, notmain - No direct push to
mainorupstream
© intel, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/xpu-ops-pr-creation of intel/torch-xpu-ops.
Open the folder on GitHubat commit a033aa5
Compare with similar skills
Xpu Ops PR Creation 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Xpu Ops PR Creation this skillintel/torch-xpu-ops | 115 | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| Create Cuda Python Pull RequestNVIDIA/cuda-python | 3.4k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| AI ReviewPaddlePaddle/Paddle | 24k | — | ~303 | Automated safety check: Pass | Apache-2.0 | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Check PRonyx-dot-app/onyx | 32k | 2 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
AI Review
PaddlePaddle/Paddle
使用 PaddlePaddle 仓库规则评审 Pull Request 和全仓库代码变更，覆盖正确性、兼容性、算子、分布式、数值、性能、安全、测试、构建和 PR 信息。当需要审查 Paddle 的代码、测试、算子 YAML、C++/CUDA/XPU kernel、Python API、分布式逻辑或 CI 配置时使用。
Finishing a Development Branch
obra/superpowers
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.
PR Babysitter
openinterpreter/openinterpreter
Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.
Check PR
onyx-dot-app/onyx
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.
Understand Diff Analysis
Egonex-AI/Understand-Anything
Reads your git changes or a pull request against a prebuilt knowledge graph of the project to explain what changed, which components are affected and what is risky.
More from intel/torch-xpu-ops
All 29 skills in this repo- Official
Intel GPU Device Selection
intel/torch-xpu-ops
Select the Intel GPU device to use when a system has multiple Intel GPU devices.
- Official
Xpu CI Health Check
intel/torch-xpu-ops
Check PyTorch ciflow/xpu (xpu.yml) on the main branch, collect the failing XPU test cases from the most recent completed run(s), analyze the ROOT CAUSE of each failure with AI, and produce a list…
- Official
At Dispatch V2
intel/torch-xpu-ops
Convert PyTorch ATDISPATCH macros to ATDISPATCHV2 format in ATen C++ code.
- Official
PR Review
intel/torch-xpu-ops
Review pull requests for XPU operator or backend code. An agent skill from intel/torch-xpu-ops.
- Official
Skill Writer
intel/torch-xpu-ops
Guide users through creating Agent Skills for Claude Code. An agent skill from intel/torch-xpu-ops.
- Official
Ut Issue Authoring
intel/torch-xpu-ops
Read the evidence a nightly UT run produced, decide which failures share a root cause and which are machine breakage rather than product bugs, and write one issue draft per root cause to drafts.json.
Related
Works with
Categories
Questions about Xpu Ops PR Creation
What does Xpu Ops PR Creation do?
How to create a pull request for the intel/torch-xpu-ops repository. Xpu Ops PR Creation is an agent skill from intel/torch-xpu-ops, published by the product's own GitHub organization. How to create a pull request for the intel/torch-xpu-ops repository.
When should I use Xpu Ops PR Creation?
Xpu Ops PR Creation fits situations like: an agent has finished implementing a fix; feature and needs to prepare a branch and PR description that satisfies CI and review requirements.
How do I install Xpu Ops PR Creation in Claude Code?
Run `npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a claude-code`. Or copy the skill folder (.claude/skills/xpu-ops-pr-creation in intel/torch-xpu-ops) into .claude/skills/xpu-ops-pr-creation in your project. Claude Code loads it when a task matches its description.
How do I install Xpu Ops PR Creation in Codex?
Run `npx skills add intel/torch-xpu-ops --skill xpu-ops-pr-creation -a codex`. Or copy the skill folder (.claude/skills/xpu-ops-pr-creation in intel/torch-xpu-ops) into .agents/skills/xpu-ops-pr-creation in your project. Codex loads it when a task matches its description.
Can I use Xpu Ops PR Creation 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 intel/torch-xpu-ops --skill xpu-ops-pr-creation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/xpu-ops-pr-creation, .gemini/skills/xpu-ops-pr-creation, .github/skills/xpu-ops-pr-creation and .opencode/skills/xpu-ops-pr-creation in your project.
What does Xpu Ops PR Creation need to run?
Going by SKILL.md and its folder, Xpu Ops PR Creation needs the command-line tools its instructions call (git and pytest).
Does Xpu Ops PR Creation access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Xpu Ops PR Creation safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Xpu Ops PR Creation use?
Xpu Ops PR Creation 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 Xpu Ops PR Creation use?
About 1.2k tokens (SKILL.md is roughly 4.6k 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 Xpu Ops PR Creation?
Skills that share tags, products or a category with Xpu Ops PR Creation: Create Cuda Python Pull Request (NVIDIA/cuda-python, 3.4k stars), AI Review (PaddlePaddle/Paddle, 24k stars), Finishing a Development Branch (obra/superpowers, 296k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Xpu Ops PR Creation?
intel (a GitHub organization, an official publisher) maintains it in intel/torch-xpu-ops, which has 115 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on October 8, 2026.
Source: intel/torch-xpu-ops on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.