Jira Status Writeback

Internal shared skill. Single source of truth for post-merge Jira status update + repair comment. Hosts declare it in dependencies, abort if missing, and pass a field map; they MUST NOT restate the two-step API or status boundary inline. This skill does not resolve PAT files; session or MCP auth follows jira-read.

When to run

Only after the PR/MR has successfully merged into the target branch. Never at PR-create time.

SOP

1. Transition (no comment on the transition call)
   • Call jira_get_transitions (or equivalent) and select the developer-owned status equivalent to「已修复」.
   • Call jira_transition_issue without a comment parameter.
   • Do not transition to close / verified / QA-owned statuses.
   • If no matching transition: skip transition, emit a warning, continue to comment if possible.