技能 jira-workflow
📦

jira-workflow

内容修订 r1 高风险 ⚙️ 外部命令🌐 网络访问🔑 环境变量

使用审批关口管理 Jira 工作流

Jira 更新常常与开发工作脱节，并需要手动跟进。此技能可帮助 Claude、Codex 或 Claude Code 提出 story、请求审批、创建 issue，并同步工作流状态。

支持: Claude Codex Code(CC)
⚠️ 38 差

使用我的智能体安装

将此请求复制给你的智能体，其中包含权威 Skill 页面和清单。

智能体请求
Review the Skillstore skill "jira-workflow" from https://skillstore.io/skills/01000001-01001110-jira-workflow.md and its manifest at https://skillstore.io/api/skills/01000001-01001110-jira-workflow/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

你的智能体仍应展示其计划，并按安全策略请求必要确认。

Agent 可读资源

当 AI Agent、爬虫或脚本需要干净上下文，而不是读取完整页面时，请使用这些链接。

Markdown 详情 GET /skills/01000001-01001110-jira-workflow.md 已签名 manifest GET /api/skills/01000001-01001110-jira-workflow/manifest 已签名 lockfile GET /api/skills/01000001-01001110-jira-workflow/lockfile

测试它

正在使用“jira-workflow”。 为密码重置邮件创建一个 Jira story。

预期结果:

一个结构化的 story 提案，包含 user story 文本、验收标准、subtask、复杂度，以及 Jira 创建前的审批问题。

正在使用“jira-workflow”。 将 SCRUM-55 移动到 active work。

预期结果:

一次 transition 检查、在可用时更新为 Progressing 状态，以及带有 issue key 的简短确认。

正在使用“jira-workflow”。 完成 SCRUM-57 并记录变更内容。

预期结果:

一段实现 comment 摘要、验证后的 Done transition，以及同步后的任务状态更新。

安全审计

高风险
v10 • 2026/7/6 打开版本化报告

Most external command and certificate findings are false positives from Markdown backticks, JavaScript template literals, and Jira issue key properties. Confirmed risks are authenticated Jira API calls and Jira credential handling through environment variables. No prompt injection or malicious exfiltration intent was found in SKILL.md.

1
已扫描文件
702
分析行数
10
复核项
0
已忽略误报

已确认安全问题 (1)

高
SKILL.md:147
Environment file access
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The example reads Jira credential material from environment variables for Basic authentication. This is expected for Jira automation, but it is still sensitive secret handling.
能力复核项 (10)

这些是真实的本地能力，对此技能可能是预期行为，因此需要复核，但不会按已确认恶意行为计分。

低
SKILL.md:174
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The example performs a fetch to the configured Jira REST API endpoint. This is intended functionality, but it is authenticated network access that can mutate Jira data if executed.
低
SKILL.md:209
Fetch API call
const response = await fetch(`${JIRA_BASE_URL}/rest/api/3/issue`, {
The example performs a fetch to the configured Jira REST API endpoint. This is intended functionality, but it is authenticated network access that can mutate Jira data if executed.
低
SKILL.md:310
Fetch API call
const response = await fetch(
The example performs a fetch to the configured Jira REST API endpoint. This is intended functionality, but it is authenticated network access that can mutate Jira data if executed.
低
SKILL.md:344
Fetch API call
const response = await fetch(
The example performs a fetch to the configured Jira REST API endpoint. This is intended functionality, but it is authenticated network access that can mutate Jira data if executed.
低
SKILL.md:412
Fetch API call
const response = await fetch(
The example performs a fetch to the configured Jira REST API endpoint. This is intended functionality, but it is authenticated network access that can mutate Jira data if executed.
低
SKILL.md:474
Fetch API call
const response = await fetch(
The example performs a fetch to the configured Jira REST API endpoint. This is intended functionality, but it is authenticated network access that can mutate Jira data if executed.
低
SKILL.md:146
Environment variable access (dot notation)
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The example reads Jira credential material from environment variables for Basic authentication. This is expected for Jira automation, but it is still sensitive secret handling.
低
SKILL.md:147
Environment variable access (dot notation)
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The example reads Jira credential material from environment variables for Basic authentication. This is expected for Jira automation, but it is still sensitive secret handling.
低
SKILL.md:146
Environment variable object
const JIRA_EMAIL = process.env.JIRA_EMAIL;
The example reads Jira credential material from environment variables for Basic authentication. This is expected for Jira automation, but it is still sensitive secret handling.
低
SKILL.md:147
Environment variable object
const JIRA_API_TOKEN = process.env.JIRA_API_TOKEN;
The example reads Jira credential material from environment variables for Basic authentication. This is expected for Jira automation, but it is still sensitive secret handling.

风险因素

⚙️ 外部命令 (87)
SKILL.md:11 SKILL.md:12 SKILL.md:13 SKILL.md:14 SKILL.md:15 SKILL.md:17 SKILL.md:31-37 SKILL.md:37-41 SKILL.md:41-42 SKILL.md:42-50 SKILL.md:50-64 SKILL.md:64-74 SKILL.md:74-77 SKILL.md:77-79 SKILL.md:79-101 SKILL.md:101-109 SKILL.md:109-137 SKILL.md:137-145 SKILL.md:145-151 SKILL.md:151-153 SKILL.md:153-174 SKILL.md:174-182 SKILL.md:182-186 SKILL.md:186-209 SKILL.md:209-217 SKILL.md:217-226 SKILL.md:226-230 SKILL.md:230-256 SKILL.md:256-261 SKILL.md:261-262 SKILL.md:262-263 SKILL.md:263-278 SKILL.md:278-300 SKILL.md:300-308 SKILL.md:308-311 SKILL.md:311-316 SKILL.md:316-322 SKILL.md:322-326 SKILL.md:326-338 SKILL.md:338-339 SKILL.md:339-340 SKILL.md:340-345 SKILL.md:345-355 SKILL.md:355-358 SKILL.md:358-361 SKILL.md:361-365 SKILL.md:365-369 SKILL.md:369-375 SKILL.md:375-381 SKILL.md:381-387 SKILL.md:387-389 SKILL.md:389-397 SKILL.md:397-413 SKILL.md:413-422 SKILL.md:422-425 SKILL.md:425-428 SKILL.md:428-432 SKILL.md:432-436 SKILL.md:436-475 SKILL.md:475-485 SKILL.md:485-493 SKILL.md:493-508 SKILL.md:508-528 SKILL.md:528-538 SKILL.md:538-551 SKILL.md:551-555 SKILL.md:555-580 SKILL.md:580-604 SKILL.md:604-605 SKILL.md:605-606 SKILL.md:606-607 SKILL.md:607-608 SKILL.md:608-609 SKILL.md:609-610 SKILL.md:610-611 SKILL.md:611-623 SKILL.md:623-628 SKILL.md:628-647 SKILL.md:647-657 SKILL.md:657-665 SKILL.md:665-669 SKILL.md:669-683 SKILL.md:683-689 SKILL.md:689 SKILL.md:690 SKILL.md:691 SKILL.md:692
🌐 网络访问 (11)
SKILL.md:174 SKILL.md:209 SKILL.md:310 SKILL.md:344 SKILL.md:412 SKILL.md:474 SKILL.md:34 SKILL.md:698 SKILL.md:699 SKILL.md:700 SKILL.md:701
🔑 环境变量 (8)
SKILL.md:146 SKILL.md:147 SKILL.md:148 SKILL.md:149 SKILL.md:146 SKILL.md:147 SKILL.md:148 SKILL.md:149
审计者: codex 查看审计历史 →
分享与引用此报告

分享版本化评估报告、中性徽章、嵌入卡片和引用。Skillstore 只报告证据，不判断该 Skill 是否安全。

打开版本化报告
安全评估

复制报告链接

https://skillstore.io/skills/01000001-01001110-jira-workflow/audits/10?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown 徽章

[![Skillstore security assessment](https://skillstore.io/badges/skills/01000001-01001110-jira-workflow/security.svg)](https://skillstore.io/skills/01000001-01001110-jira-workflow?utm_source=security_passport_badge)

HTML 徽章

<a href="https://skillstore.io/skills/01000001-01001110-jira-workflow?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/01000001-01001110-jira-workflow/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

嵌入卡片

<iframe src="https://skillstore.io/embed/skills/01000001-01001110-jira-workflow.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
学术引用 (APA · BibTeX · CFF)

APA 引用

01000001-01001110. (2026). jira-workflow security audit report (audit version 10) [Author version unspecified]. Skillstore. https://skillstore.io/skills/01000001-01001110-jira-workflow/audits/10

BibTeX 引用

@techreport{01000001-01001110-01000001-01001110-jira-workflow-2026, author = {01000001-01001110}, title = {jira-workflow security audit report (audit version 10)}, institution = {Skillstore}, year = {2026}, number = {10}, url = {https://skillstore.io/skills/01000001-01001110-jira-workflow/audits/10}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "jira-workflow security audit report (audit version 10)" version: "unspecified" type: report authors: - name: "01000001-01001110" date-released: "2026-07-06" url: "https://skillstore.io/skills/01000001-01001110-jira-workflow/audits/10" identifiers: - type: other value: "skillstore:01000001-01001110-jira-workflow:audit:10" description: "Skillstore immutable audit report identifier"

Skillstore 评分

评分依据 证据置信度: 中
55
架构
85
可维护性
87
内容
73
社区
74
规范符合性

你能构建什么

准备已审批的 Jira story

在创建 issue 之前，将功能请求转化为结构化的 Jira story 提案。

保持开发状态最新

在编码工作开始和完成时，将 Jira issue 推进到 Progressing 和 Done。

协调 sprint 执行

创建 subtask、添加实现说明，并在 sprint 工作期间维护工作流状态。

试试这些提示

起草 Jira story 
为此功能创建一个 Jira story 提案。包括 persona、goal、benefit、acceptance criteria、complexity 和 subtasks。创建前先请求审批。
创建已审批的 issue 
使用已审批的 story 详情，在我配置的项目中创建一个 Jira issue。如果适用，将其链接到此 epic，然后报告新的 issue key。
同步工作进度 
开始处理此 Jira issue，更新我的任务列表，并添加一条简洁的进度 comment。在更改 Jira 状态之前查询可用的 transitions。
完成一个工作流周期 
为此已审批任务运行完整的 Jira 工作流。创建 issue，在工作开始时 transition 它，添加实现说明，并在验证后完成它。

最佳实践

  • 在执行每个 Jira 创建、comment 和 transition 操作之前进行确认。
  • 仅为目标项目使用最小权限的 Jira API token。
  • 在任何 Jira 项目中更改状态之前，先查询可用的 transitions。

避免

  • 不要在未经用户审批的情况下，根据模糊请求创建 Jira issue。
  • 不要假设不同 Jira 项目中的工作流状态名称一致。
  • 不要将 Jira API token 粘贴到 prompt、comment 或 issue 描述中。

常见问题

此技能会自动创建 Jira issue 吗？
它会指示助手在创建 Jira issue 之前请求审批。
它支持哪些 Jira 项目？
它面向 Jira Cloud REST API v3 和团队管理型工作流编写，并包含 classic epic links 的说明。
需要哪些凭据？
它需要 Jira email、API token、base URL、project key，以及可选的 board ID 环境变量。
它可以 transition Jira issue 吗？
可以。它会查询可用的 transitions，然后在存在匹配项时发布对应的 transition。
它可以添加实现说明吗？
可以。它提供了添加 comment 的示例，内容包括文件、commit 和完成说明。
是否包含可执行的辅助脚本？
不包含。扫描到的包中只有 SKILL.md，尽管文本中引用了脚本。

开发者详情

许可证

MIT

Skillstore 修订

r1

版本提示

作者未声明版本。

仓库

https://github.com/01000001-01001110/agent-jira-skills/tree/main/jira-safe/jira-workflow

引用

2e36836131679643f7a49e4cfff588d67adc404b

维护新鲜度

2026/7/18

使用量

58 次下载 · 404 次浏览

文件结构

📄 SKILL.md

01000001-01001110 的更多技能

查看全部

相关技能

查看全部