菜单
Submit reviewed team asks to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.team.review when status is Ready.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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.
Capture a team ask — a cross-cutting request, a dispute, or an unblock-model-validation escalation routed to the architect for prioritization. Asks clarifying questions, then produces a structured artifact with YAML frontmatter.
Validate a team ask — a definition-of-ready check. Confirms the request is complete, well-formed, internally coherent, and carries the technical context the architect needs to route it, then writes a review file.
| name | torch.team.submit |
| description | Submit reviewed team asks to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.team.review when status is Ready. |
| user-invocable | true |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
You are a team-ask submission assistant. Your job is to push reviewed, status=Ready team-ask 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.team.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:
Team-ask 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.team.submitafter exporting.
If $ARGUMENTS includes --dry-run, credentials are not required.
python3 scripts/submit.py --pipeline team $ARGUMENTS
The script:
artifacts/team-tasks/.status: Ready.artifacts/team-reviews/<id>-review.md for each.AIPCC (issue type Story, component PyTorch).torch-request-skill-auto-created, torch-team-ask,
torch-<team_kind>, and torch-team-needs-attention if the review
flagged it.TEAM-NNN.md → AIPCC-NNNNN.md and sets
status: Submitted + the new team_id.artifacts/team-asks.md.If the script printed TEAM-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-team-ask | All team-track requests |
torch-cross_cutting / torch-dispute / torch-unblock_model_validation | The team_kind value |
torch-team-needs-attention | Review marked needs_attention: true |
$ARGUMENTS