Official agent skill

Auto Label

Rules for automatically determining which disable labels to apply to a PR based on the file paths changed.

OfficialApache-2.0Auto-check passedTesting & QA

Install Auto Label

skills CLI

$ npx skills add intel/torch-xpu-ops --skill auto-label -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops auto-label --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/auto-label .claude/skills/auto-label && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "auto-label" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label into .claude/skills/auto-label/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-label", 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

$skill-installer install https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label

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 intel/torch-xpu-ops --skill auto-label -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops auto-label --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/auto-label .agents/skills/auto-label && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "auto-label" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label into .agents/skills/auto-label/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-label", 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 intel/torch-xpu-ops --skill auto-label -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops auto-label --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/auto-label .cursor/skills/auto-label && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "auto-label" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label into .cursor/skills/auto-label/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-label", 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

$ gemini skills install https://github.com/intel/torch-xpu-ops.git --path .claude/skills/auto-label

--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 intel/torch-xpu-ops --skill auto-label -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops auto-label --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/auto-label .gemini/skills/auto-label && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "auto-label" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label into .gemini/skills/auto-label/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-label", 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.

GitHub CLI

$ gh skill install intel/torch-xpu-ops auto-label

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 intel/torch-xpu-ops --skill auto-label -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/auto-label .github/skills/auto-label && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "auto-label" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label into .github/skills/auto-label/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-label", 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 intel/torch-xpu-ops --skill auto-label -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install intel/torch-xpu-ops auto-label --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/intel/torch-xpu-ops.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/auto-label .opencode/skills/auto-label && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "auto-label" agent skill from https://github.com/intel/torch-xpu-ops/tree/main/.claude/skills/auto-label into .opencode/skills/auto-label/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "auto-label", 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: auto-label
GitHub stars: 115
Token cost: ~1.7k tokens
SKILL.md length: 769 words
Files: 1
Skills in repo: 29
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Rules for automatically determining which disable labels to apply to a PR based on the file paths changed.

Works in 3 steps: disable_auto label — When manually added… → PRs with ai_generated label should still… → When in doubt, disable less. It's better…
Testing & QA work in your project
SKILL.md covers Purpose, Available Labels, Decision Rules and disable_build Logic…, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Auto Label is an agent skill from intel/torch-xpu-ops, published by the product's own GitHub organization. Rules for automatically determining which disable labels to apply to a PR based on the file paths changed. Used by the auto-label workflow.

Its SKILL.md is about 1.7k 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 Testing & QA. It works with GitHub Actions, Linux and GitHub. The licence is Apache-2.0.

When your agent uses it

Testing & QA work in your project

Example prompts

“Use the auto-label skill to rule for automatically determining which disable labels to apply to a PR based on the file paths changed”
“/auto-label”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

disable_auto label — When manually added to a PR, auto-labeling is completely disabled for that PR. The workflow will skip without…
PRs with ai_generated label should still follow these rules (they need CI validation).
When in doubt, disable less. It's better to run unnecessary CI than to miss a regression.

What it can do on your machine

Read from SKILL.md and the folder at commit 0187b3b. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Auto Label loads about 1.7k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 769 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~38
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

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 0187b3b, republished under its Apache-2.0 licence (© intel). 769 words, ~1,701 tokens.

Download SKILL.mdSave it as .claude/skills/auto-label/SKILL.md (or your agent's skills folder).

name: auto-label
description: Rules for automatically determining which disable_* labels to apply to a PR based on the file paths changed. Used by the auto-label workflow.

PR Auto-Labeling Rules

Purpose

Determine which disable_* CI labels to apply to a PR based on the files changed. These labels control which CI jobs run, reducing unnecessary CI load.

Available Labels

Label	Effect
`disable_all`	Skip all CI test jobs, only run lint
`disable_ut`	Skip non-distributed UT jobs
`disable_e2e`	Skip e2e (inductor benchmark) jobs
`disable_distributed`	Skip distributed UT jobs
`disable_win`	Skip Windows CI jobs
`disable_build`	Skip source build, use nightly wheel

Note: Only labels consumed by pull.yml are in scope. Other labels (disable_accelerate, disable_transformers) are used by separate workflows and not managed here.

Decision Rules

Evaluate the file paths changed in the PR and apply labels using the following logic. Rules are evaluated top-to-bottom; use the FIRST matching rule set.

Rule 1: Pure CI metadata (no functional logic change)

Condition: ALL changed files match .github/ISSUE_TEMPLATE/, .github/copilot-instructions.md, .claude/, test/agentic/, or other non-functional metadata files. No .github/workflows/, .github/actions/, or .github/scripts/ changes.

Labels: disable_all

Examples: Updating issue templates, adding skills docs, agentic test fixtures.

Rule 2: CI workflow / action / script changes

Condition: Changed files include .github/workflows/, .github/actions/, or .github/scripts/.

Labels: Determined by WHICH workflows/actions/scripts are modified:

If modifying _linux_build.yml or build-related actions/scripts → keep linux-build running, disable others: disable_ut,disable_e2e,disable_distributed,disable_win
If modifying _linux_ut.yml or UT-related actions/scripts → keep linux-ut running: disable_e2e,disable_distributed,disable_win
If modifying _linux_e2e.yml or e2e-related actions/scripts → keep linux-e2e running: disable_ut,disable_distributed,disable_win
If modifying _windows_*.yml → keep windows jobs running, add windows_ci: disable_ut,disable_e2e,disable_distributed
If modifying pull.yml only (trigger/condition/concurrency changes) → disable_all
If modifying only non-functional workflows (auto_label.yml, auto_merge_by_comment.yml, issue_operator.yml, bot.yml) or bot scripts (.github/scripts/bot_*.py) → disable_all
If modifying MULTIPLE workflow areas or unclear scope → run full CI: none

Additional: If no src/, cmake/, CMakeLists.txt files changed, add disable_build.

Rule 3: Only skip/expect list changes

Condition: ALL changed files are test/xpu/skip_list_common.py, test/xpu/expect/, test/xpu/extended/skip_list_*.py, or test/xpu/test_decomp_xpu.py (pure skip list / expect file updates with no test logic change).

Labels: disable_all

Rationale: Skip list changes don't need functional validation beyond lint.

Rule 4: Test infrastructure changes

Condition: Changed files include test/xpu/xpu_test_utils.py or test/xpu/run_test_with_skip.py (test infrastructure used by all test suites).

Labels: disable_e2e, disable_distributed

Rationale: Test infrastructure affects all UT suites across platforms, so UT must run and disable_win must NOT be added. E2E and distributed use separate infrastructure.

Additional: Always add disable_build (test-only changes don't need source build).

Rule 5: Test-only changes

Condition: ALL changed files are under test/ (excluding files handled by Rules 3-4).

Labels (base): disable_e2e, disable_distributed

Additional modifiers:

If files are ONLY under test/xpu/functorch/ or test/xpu/dynamo/ or test/xpu/higher_order_ops/: add disable_win
If NO files under paths covered by Windows UT (test/xpu/test_ops*.py, test/xpu/core/, test/xpu/test_nn*.py): add disable_win

Additional: Always add disable_build (test-only changes don't need source build).

Show full SKILL.md (346 more words)Show less

Rule 6: Kernel/operator source changes (src/)

Condition: Changed files include src/ATen/ or src/xccl/ (but NOT src/*.cmake, src/CMakeLists.txt, or src/Build*.cmake — those are build system files, see Rule 7).

Labels: Depends on which subdirectory:

src/ATen/ only (kernel/operator code, no xccl):
- Base: disable_e2e, disable_distributed
- Do NOT add disable_win — kernel fixes may be platform-specific (e.g. a fix specifically for Windows)
src/xccl/ involved (distributed communication backend):
- Base: disable_e2e only — do NOT add disable_distributed (xccl changes must run distributed tests)
- Add disable_win (xccl is Linux-only)

Note: Do NOT add disable_build — source changes require compilation.

Rule 7: Build system changes

Condition: Changed files include cmake/, CMakeLists.txt, src/**/*.cmake, src/Build*.cmake, or tools/.

Labels: None (or minimal). Build system changes need full CI validation.

If ONLY build system files changed (no test, no kernel): disable_e2e, disable_distributed

Rule 8: Mixed changes (fallback)

Condition: None of the above rules fully apply (mixed src + test + CI, etc.).

Labels: Apply the INTERSECTION of what each individual file category would disable.

If any src/ file changed: do NOT add disable_build
If any cmake//CMakeLists.txt changed: do NOT add disable_build
Only disable a job if ALL changed files agree it should be disabled

disable_build Logic (cross-cutting)

disable_build can be added whenever ALL of these are true:

No files changed in src/ (excluding src/**/*.py)
No files changed in cmake/
No CMakeLists.txt changed
No files changed in tools/ that affect the build

When disable_build is applied, CI uses nightly wheel instead of building from source.

Output Format

When used by the auto-label workflow, output ONLY the label names as a comma-separated list:

disable_e2e,disable_distributed,disable_win

If no labels should be applied (full CI needed), output:

none

Important Notes

disable_auto label — When manually added to a PR, auto-labeling is completely disabled for that PR. The workflow will skip without allocating a runner. This label should only be added manually by humans (never by automation) to opt out of auto-labeling when full manual control over CI labels is needed.
PRs with ai_generated label should still follow these rules (they need CI validation).
When in doubt, disable less. It's better to run unnecessary CI than to miss a regression.

Files

Just SKILL.md in .claude/skills/auto-label of intel/torch-xpu-ops.

Open the folder on GitHubat commit 0187b3b

Compare with similar skills

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

Auto Label compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Auto Label this skillintel/torch-xpu-ops	115	—	~1.7k	Automated safety check: Pass	Apache-2.0	yesterday
Release Allpaperboytm/spool	592	—	~1.1k	Automated safety check: Pass	Custom licence	2 mo ago
Releasing MarchatCod-e-Codes/marchat	137	—	~801	Automated safety check: Pass	MIT	4 days ago
GitHub Runnermagnus919/agent-skills	111	—	~1.7k	Automated safety check: Pass	MIT	yesterday
GreptimeDB Fuzz CI Failure InvestigationGreptimeTeam/greptimedb	6.7k	—	~4.4k	Automated safety check: Pass	Apache-2.0	2 days ago
Detect Flaky Testsagent-substrate/substrate	4.5k	—	~3k	Automated safety check: Pass	Apache-2.0	today

Similar skills

Release All
paperboytm/spool
Publish the complete Spool CLI release train: synchronized versions, npm packages, the GitHub release, and the matching production web deployment.
592 GitHub stars~1.1k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Releasing Marchat
Cod-e-Codes/marchat
Prepares marchat releases: version bumps, CHANGELOG, packaging checksums, GitHub Actions release workflow, and Docker tags.
137 GitHub stars~801 tokensUpdated 4 days ago
DevOps & CloudAuto-check passed
GitHub Runner
magnus919/agent-skills
Deploy, manage, and troubleshoot self-hosted GitHub Actions runners.
111 GitHub stars~1.7k tokensUpdated yesterday
DevOps & CloudAuto-check passed
GreptimeDB Fuzz CI Failure Investigation
GreptimeTeam/greptimedb
Diagnoses a failed GreptimeDB fuzz CI job by pulling its GitHub Actions logs and fuzz artifacts, then matching the evidence to the local source code.
6.7k GitHub stars~4.4k tokensUpdated 2 days ago
Testing & QAAuto-check passed
Detect Flaky Tests
agent-substrate/substrate
Detects flaky Go tests by analyzing GitHub Actions workflow runs across the last 7 days and all PRs — covering both the run-tests job (unit/integration) and the e2e-test job (gVisor and microVM…
4.5k GitHub stars~3k tokensUpdated today
Testing & QAAuto-check passed
Review
apollographql/apollo-mcp-server
Review a GitHub pull request for a Rust codebase. An agent skill from apollographql/apollo-mcp-server.
311 GitHub stars~2.9k tokensUpdated today
Testing & QAAuto-check passed

More from intel/torch-xpu-ops

All 29 skills in this repo

Intel GPU Device Selection
intel/torch-xpu-ops
Official
Select the Intel GPU device to use when a system has multiple Intel GPU devices.
115 GitHub stars~508 tokensUpdated yesterday
Auto-check passed
Xpu CI Health Check
intel/torch-xpu-ops
Official
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…
115 GitHub stars~1.5k tokensUpdated yesterday
Auto-check passed
At Dispatch V2
intel/torch-xpu-ops
Official
Convert PyTorch ATDISPATCH macros to ATDISPATCHV2 format in ATen C++ code.
115 GitHub starsUsed in 3 repos~2.2k tokens
Auto-check passed
PR Review
intel/torch-xpu-ops
Official
Review pull requests for XPU operator or backend code. An agent skill from intel/torch-xpu-ops.
115 GitHub stars~4.2k tokensUpdated yesterday
Auto-check passed
Skill Writer
intel/torch-xpu-ops
Official
Guide users through creating Agent Skills for Claude Code. An agent skill from intel/torch-xpu-ops.
115 GitHub starsUsed in 3 repos~2.4k tokens
Auto-check passed
Ut Issue Authoring
intel/torch-xpu-ops
Official
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.
115 GitHub stars~2k tokensUpdated yesterday
Auto-check passed

Works with

Questions about Auto Label

What does Auto Label do?

Rules for automatically determining which disable labels to apply to a PR based on the file paths changed. Auto Label is an agent skill from intel/torch-xpu-ops, published by the product's own GitHub organization. Rules for automatically determining which disable labels to apply to a PR based on the file paths changed.

When should I use Auto Label?

Auto Label fits situations like: testing & QA work in your project.

How do I install Auto Label in Claude Code?

Run `npx skills add intel/torch-xpu-ops --skill auto-label -a claude-code`. Or copy the skill folder (.claude/skills/auto-label in intel/torch-xpu-ops) into .claude/skills/auto-label in your project. Claude Code loads it when a task matches its description.

How do I install Auto Label in Codex?

Run `npx skills add intel/torch-xpu-ops --skill auto-label -a codex`. Or copy the skill folder (.claude/skills/auto-label in intel/torch-xpu-ops) into .agents/skills/auto-label in your project. Codex loads it when a task matches its description.

Can I use Auto Label 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 auto-label -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/auto-label, .gemini/skills/auto-label, .github/skills/auto-label and .opencode/skills/auto-label in your project.

What does Auto Label need to run?

SKILL.md names no scripts, command-line tools or credentials: Auto Label is instructions for the agent only.

Does Auto Label access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Auto Label 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 Auto Label use?

Auto Label 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 Auto Label use?

About 1.7k tokens (SKILL.md is roughly 6.8k 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 Auto Label?

Skills that share tags, products or a category with Auto Label: Release All (paperboytm/spool, 592 stars), Releasing Marchat (Cod-e-Codes/marchat, 137 stars), GitHub Runner (magnus919/agent-skills, 111 stars) and GreptimeDB Fuzz CI Failure Investigation (GreptimeTeam/greptimedb, 6.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Auto Label?

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

Install Auto Label

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

PR Auto-Labeling Rules

Purpose

Available Labels

Decision Rules

Rule 1: Pure CI metadata (no functional logic change)

Rule 2: CI workflow / action / script changes

Rule 3: Only skip/expect list changes

Rule 4: Test infrastructure changes

Rule 5: Test-only changes

Rule 6: Kernel/operator source changes (src/)

Rule 7: Build system changes

Rule 8: Mixed changes (fallback)

disable_build Logic (cross-cutting)

Output Format

Important Notes

Files

Compare with similar skills

Similar skills

More from intel/torch-xpu-ops

Related

Questions about Auto Label