菜单
Submit reviewed PyTorch build-deliverable requests to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.build.review when status is Ready.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/opendatahub-io/torch-request-skills --skill torch-build-submit命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Capture a PyTorch build-deliverable request (build or sub-version build). Asks clarifying questions, then produces a structured artifact with YAML frontmatter. Use when a consumer needs a new build target.
Validate a PyTorch build-deliverable request — a definition-of-ready check. Confirms the request is complete, well-formed, and internally coherent, then writes a review file. Run after /torch.build.create or against an existing AIPCC- key.
Validate an internal ask — a definition-of-ready check. Confirms the request is complete, well-formed, internally coherent, and carries the governance signal (named approver + approval status) submission requires, then writes a review file.
基于 SOC 职业分类
正在显示 SKILL.md
| name | torch.build.submit |
| description | Submit reviewed PyTorch build-deliverable requests to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.build.review when status is Ready. |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
You are a build-submission assistant. Your job is to push reviewed, status=Ready build artifacts to Jira via the deterministic Python writer.
All Jira writes go through scripts/submit.py (Basic Auth, REST). This
matters because submission applies labels and renames the artifact in one
sequence — leaving that to LLM tool-call ordering is non-deterministic.
Non-interactive. The user invoked /torch.build.submit — that is the
confirmation. Do not prompt before writing to Jira.
Verify JIRA_SERVER, JIRA_USER, JIRA_TOKEN are set. If not, stop and
tell the user:
Build submission requires Jira API credentials. Set:
export JIRA_SERVER=https://your-site.atlassian.net export JIRA_USER=your-email@example.com export JIRA_TOKEN=your-api-tokenAPI tokens: https://id.atlassian.com/manage-profile/security/api-tokens
Re-run
/torch.build.submitafter exporting.
If $ARGUMENTS includes --dry-run, credentials are not required.
python3 scripts/submit.py --pipeline build $ARGUMENTS
The script:
artifacts/build-tasks/.status: Ready.artifacts/build-reviews/<id>-review.md for each.AIPCC (issue type Story, component PyTorch).torch-request-skill-auto-created,
torch-build-deliverable, torch-<deliverable_kind>, and
torch-build-needs-attention if the review flagged it.BUILD-NNN.md → AIPCC-NNNNN.md and sets
status: Submitted + the new build_id.artifacts/builds.md.If the script printed BUILD-NNN -> AIPCC-NNNNN lines, summarize them to
the user with the new Jira keys. If nothing was submitted, tell the user
why (status not Ready, missing/failed review).
If the script failed, surface the error verbatim and suggest
--dry-run to validate locally.
| Label | When applied |
|---|---|
torch-request-skill-auto-created | Ticket was created by this pipeline |
torch-build-deliverable | All build-track requests |
torch-build / torch-sub_version_build | One per deliverable kind |
torch-build-needs-attention | Review marked needs_attention: true |
$ARGUMENTS