SkillsAdd

fudesign2008/open-skills

jira-status-writeback

Post-merge Jira writeback SOP: transition only to「已修复」, then independent jira_add_comment with body.

First seen Jul 28, 2026

Installation

$ npx skills add fudesign2008/open-skills --skill jira-status-writeback
View on skills.sh ↗ GitHub repository ↗

Summary

  • Post-merge Jira writeback SOP: transition only to「已修复」, then independent jira_add_comment with body.
  • 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.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

frontend-design Same topic
anthropics/skills

Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…

866.4K installs
agent-browser Same topic
vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, includ…

810.4K installs
vercel-react-best-practices Same topic
vercel-labs/agent-skills 697.8K installs
web-design-guidelines Same topic
vercel-labs/agent-skills

Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…

617.3K installs
microsoft-foundry Same topic
microsoft/azure-skills

Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …

576.5K installs
azure-diagnostics Same topic
microsoft/azure-skills

Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …

568.9K installs

Also in this package

Other skills from fudesign2008/open-skills · top by installs.

npx skills add fudesign2008/open-skills
jira-fix-workflow 73 solve-workflow 71 opsx-solve-workflow 69 opsx-jira-fix-workflow 68 typescript-check 67 android-webview-debug 67 jira-read 66 git-commit 66 opsx-jira-fix-batch 65 think-big 64

Browse all from fudesign2008/open-skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 6
License LICENSE
Default branch main
Open issues 0
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.1

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,700 B
  • docs SUMMARY.md 406 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 35 installs

SKILL.md

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 jiragettransitions (or equivalent) and select the developer-owned status equivalent to「已修复」. - Call jiratransitionissue 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.

  1. Comment (independent call)

- Call jiraaddcomment(issuekey=..., body=...). - The comment text parameter name is body (not comment). - Never rely on jiratransition_issue's comment parameter for the repair record (it may be silently dropped).

  1. Failure handling

- Transition or comment API failure → warn and record for the host report; do not block or revert an already-completed merge.

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-writeback in frontmatter dependencies.
  • 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.