jira-status-writeback
Post-merge Jira writeback SOP: transition only to「已修复」, then an independent Wiki-markup comment posted in the body field with read-back markup-fidelity verification and a direct-REST fallback. Triggers — 「Jira 状态回写」「回写已修复」「合并后写 Jira」「jira writeback」「jira status writeback」. Do NOT use for reading issues, creating issues, or pre-merge comments. Loaded by Jira fix hosts after merge via frontmatter dependencies.
How do I install this agent skill?
npx skills add https://github.com/fudesign2008/open-skills --skill jira-status-writebackIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill is a Jira status writeback utility that handles issue transitions and wiki-markup comments. It uses a documented credential chain for Jira authentication and includes a fallback script with markup fidelity checks. No malicious behavior was detected.
- Socketwarn
1 alert: gptAnomaly
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
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. The SOP does not resolve PAT files; session or MCP auth follows thejira-readcredential contract. The bundled REST fallback resolves credentials through that same contract and expects both skills under one skills root.Prerequisite check:
jira-status-lifecycle,jira-wiki-markup, andjira-readmust all be available; if any is missing, abort and print the standard install hint (npx skills add FuDesign2008/open-skills -g --skill '*' --yes).
When to run
Only after the PR/MR has successfully merged into the target branch. Never at PR-create time.
SOP
-
Transition (no comment on the transition call)
- Call
jira_get_transitions(or equivalent) first and record whether a transition to thefixedstatus exists. - Load
jira-status-lifecycleand rundecidePostMergewith the session user, assignee, status class, and that boolean. - When the decision's
transitionis true, select the developer-owned status equivalent to「已修复」and calljira_transition_issuewithout acommentparameter. Pass booleantruetoapplyTransitionResultonly when that call succeeded. Passfalsefor every other result. Do not pass the raw API result. - Do not transition to close / verified / QA-owned statuses.
- When the decision's
notifyis true, tell the operator the status was left unchanged because the issue is not assigned to the session user. - When the outcome is
incomplete-identity,incomplete-not-assignee, orincomplete-transition, keep the merge and leave the lifecycle incomplete. Do not describe the bug as「已修复」.
- Call
-
Comment (independent call, verify markup fidelity)
- Post this step when the lifecycle decision's
commentis true, including afterincomplete-identityandincomplete-transition. Skip it forincomplete-not-assignee. - Load
jira-wiki-markupand composebodyfrom the host field map using that skill's canonical repair-comment skeleton (Wiki markup). - If any line of that repair
bodystarts withh1.orh2., rewrite those titles as numbered# *name*items so the comment stays ath3./h4.plus lists. - Post via your available comment tooling with the text in the
bodyfield. Never rely onjira_transition_issue'scommentparameter for the repair record (it may be silently dropped). - Verify fidelity before declaring done: read back the stored
bodyfrom the tool response (or a follow-up read) and compare it against the composed text — line-start headings (h3./h4.),*bold*,{{mono}}, and[label|url]must all survive verbatim. A 2xx response alone is NOT success: an intermediate layer may escape markup (store*bold*as\*bold\*) or rewrite headings (h3. Xinto### X) and still return 2xx. - On any fidelity failure, rewrite the comment with the bundled REST fallback
scripts/update-comment-wiki.mjs(comment bodies only; credential chain identical tojira-read; pass no comment id to create, pass the comment id to update; it re-verifies fidelity on its own), then report from its PASS output.
- Post this step when the lifecycle decision's
-
Failure handling
- When the outcome is
incomplete-transition, the lifecycle stays incomplete and the repair comment still posts. The merge stays.status-satisfiedapplies only whendecidePostMergereturns it for an issue alreadyfixedand assigned to the session user.incomplete-not-assigneestays incomplete and does not post the repair comment, including when the status is alreadyfixed. - A comment API failure after a successful transition warns and records for the host report. The merge stays, and the status obligation already met stays met.
- A missing prerequisite at load aborts writeback. The merge stays, and the host leaves the lifecycle incomplete.
- When the outcome is
Host field map
Hosts MUST supply concrete values for these semantic fields (omit a field only when truly N/A, and say so):
| Field | Meaning |
|---|---|
| Fix branch | Source branch name |
| Commit | Merged tip SHA or primary fix commit |
| PR/MR URL | Merge request URL |
| Root cause | Short root-cause summary |
| Fix summary | What changed |
| Changed files | Key paths |
| Verification | Functional / boundary / regression notes (hosts may require ≥2 each) |
| Extra | Host-specific: analysis report path (jira-fix-workflow), OpenSpec change path (opsx-jira-fix-workflow), QA risks, etc. |
Integration
- Declare
jira-status-writebackin frontmatterdependencies. - At writeback: load this skill, pass the field map, follow the SOP.
- Keep in the host: when writeback runs in the stage order (after merge; after archive when required), and the field map only.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/fudesign2008/open-skills/jira-status-writeback">View jira-status-writeback on skillZs</a>