torch-xpu-ops
Copilot instructions121 starsChanged 5 months agoApache-2.0View on GitHub
All agent instructions live in CLAUDE.md at the repository root. You MUST read the linked file in full before proceeding. Do not skip this step. Do not paraphrase from memory. The contents of these files are authoritative. When invoked to review a PR — the comment contains "review", "/pr-review", "/skill-writer", or any similar analysis request — the response is a single markdown comment on the PR. No file edits, no commits, no new branches. Findings that could be fixed directly…
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,349 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- asm-source-mappingSkill
- at-dispatch-v2Skill
- auto-labelSkill
- extract-asm-onednnSkill
- extract-asm-syclkernel-aotSkill
- extract-asm-syclkernel-jitSkill
- extract-asm-tritonSkill
- extract-xpu-kernel-asmSkill
- fix-implementSkill
- fix-reproduceSkill
- fix-root-causeSkill
- fix-verifySkill
- issue-handlerSkill
- issue-triageSkill
- label-issueSkill
- oob-perf-analysisSkill
- pr-reviewSkill
- release-branchingSkill
- skill-writerSkill
- ut-checkSkill
- ut-issue-authoringSkill
- ut-refactor-reviewSkill
- xpu-alignmentSkill
- xpu-build-pytorchSkill
- xpu-ci-health-checkSkill
- xpu-ops-pr-creationSkill
- xpu-release-notesSkill
The file
We split this copilot-instructions.md into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 5
All agent instructions live in CLAUDE.md at the repository root.
- Distinctive: line 16
When invoked to review a PR — the comment contains "review", "/pr-review", "/skill-writer", or any similar analysis request — the response …
- Distinctive: line 18
single markdown comment on the PR: No file edits, no commits, no new branches.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Copilot Instructions — torch-xpu-ops
Required reading (mandatory)
All agent instructions live in CLAUDE.md at the repository root. You MUST read the linked file in
full before proceeding. Do not skip this step. Do not paraphrase from
memory. The contents of these files are authoritative.
| When you are about to... | Read this file first |
| All agent instructions | CLAUDE.md |
| Review a pull request | .claude/skills/pr-review/SKILL.md |
Review mode is read-only
When invoked to review a PR — the comment contains "review", "/pr-review", "/skill-writer", or any similar analysis request — the response is a single markdown comment on the PR. No file edits, no commits, no new branches. Findings that could be fixed directly must be described in the comment for the author to apply.
The user can request code changes in a separate follow-up comment with an explicit action verb ("fix", "apply", "commit"). Do not preemptively combine review with modification, even when the fix looks trivial — splitting the two keeps the review reproducible and lets the author audit diffs before they land.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.