菜单
Use when user asks to create a version release ticket, says "帮我建个发版任务", "建个 Jira", "创建发版单", or needs to track an SDK release in Jira
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a feature, bugfix, or refactoring step is completed and needs review, or before merging to main, or when user says "review", "审查", "帮我看看代码"
Use when receiving an ambiguous feature request, when scope is unclear, or before writing any plan
Use after verification-before-completion passes and code review is clean, to close out the development branch
Use when executing git commit, creating or naming branches, writing PR titles/descriptions, or asking about commit message format, branch naming, or version numbering in this project
Use when writing or reviewing .ets/.ts files in this project, or when seeing any, unknown, obj['key'] index access, destructuring assignment, var declarations,
Use when user mentions "发布 SDK"、"ohpm 发布"、"打包发布"、"上传 har"、"publish"、"发版"、"release"、"发布" or "上传" in the context of this SDK
| name | jira-ticket |
| description | Use when user asks to create a version release ticket, says "帮我建个发版任务", "建个 Jira", "创建发版单", or needs to track an SDK release in Jira |
Type: Reference | Discipline: Flexible
创建 SDK 版本发布的 Jira Ticket。
适用：
不适用：
jira-ticket release detect # 检测版本
jira-ticket release create # 创建 Ticket
jira-ticket release create --dry-run # 预览
jira-ticket release create --yes # 跳过确认
需设置 JIRA_TOKEN，可选 JIRA_URL 和 DEFAULT_PROJECT_KEY。
| 想法 | 现实 |
|---|---|
| "等发完版再建 ticket" | 先建 ticket 再发版，版本号和 ticket ID 关联性才清晰 |
| "dry-run 跑过就等于建成了" | --dry-run 不落盘，必须去掉才实际创建 |
"--yes 跳过确认省事" | 生产流程建议先交互确认，自动化脚本才用 --yes |
"JIRA_TOKEN 过期就注释掉校验" | 过期一定要重新生成 token，不可绕过鉴权 |
ohpm-publish 之前）ohpm-publish 发布 HAR → 发版完成后回到 ticket 更新状态