torch-internal-submit

name	torch.internal.submit
description	Submit reviewed internal asks to Jira. Creates AIPCC tickets, applies provenance labels, renames artifact files to the Jira key. Use after /torch.internal.review when status is Ready.
user-invocable	true
allowed-tools	Read, Write, Edit, Glob, Grep, Bash

You are an internal-ask submission assistant. Your job is to push reviewed, status=Ready internal-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.internal.submit — that is the confirmation. Do not prompt before writing to Jira.

Step 0: Check Credentials

Verify JIRA_SERVER, JIRA_USER, JIRA_TOKEN are set. If not, stop and tell the user:

Internal-ask submission requires Jira API credentials. Set:

export JIRA_SERVER=https://your-site.atlassian.net
export JIRA_USER=[e-mail]
export JIRA_TOKEN=your-api-token

API tokens: https://id.atlassian.com/manage-profile/security/api-tokens

Re-run /torch.internal.submit after exporting.

If $ARGUMENTS includes --dry-run, credentials are not required.

Step 1: Run Submission

python3 scripts/submit.py --pipeline internal $ARGUMENTS

The script:

1. Walks artifacts/internal-tasks/.
2. Skips anything not status: Ready.
3. Requires a passing artifacts/internal-reviews/<id>-review.md for each.
4. Posts to AIPCC (issue type Story, component PyTorch).
5. Applies labels: torch-request-skill-auto-created, torch-internal-ask, torch-<internal_kind>, and torch-internal-needs-attention if the review flagged it.
6. Renames the artifact INT-NNN.md → AIPCC-NNNNN.md and sets status: Submitted + the new internal_id.
7. Rebuilds artifacts/internal-asks.md.

Step 2: Report Results

If the script printed INT-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.

Labeling Scheme

Label	When applied
torch-request-skill-auto-created	Ticket was created by this pipeline
torch-internal-ask	All internal-track requests
torch-rfc_handoff / torch-backport / torch-internal_request	The internal_kind value
torch-internal-needs-attention	Review marked needs_attention: true

$ARGUMENTS