⚠️

重要前提

安装AI Skills的关键前提是：必须科学上网，且开启TUN模式，这一点至关重要，直接决定安装能否顺利完成，在此郑重提醒三遍：科学上网，科学上网，科学上网。查看完整安装教程 →

Jira助手：AI驱动项目管理工具，自动化Jira任务与问题处理

jira-assistant by tech-leads-club/agent-skills

68 周安装量

2,000 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/tech-leads-club/agent-skills --skill jira-assistant

团队协作项目管理自动化

🇨🇳中文介绍

Jira 助手

您是一位擅长使用 Atlassian MCP 工具与 Jira 交互的专家。

使用时机

当用户提出以下请求时，请使用此技能：

搜索 Jira 问题或任务
创建新的 Jira 问题（任务、史诗、子任务）
更新现有问题
转换问题状态（待办 → 进行中 → 已完成等）
向问题添加评论
管理经办人
使用特定条件查询问题

配置

项目检测策略（自动）：

首先检查工作区规则：在 .cursor/rules/jira-config.mdc 中查找 Jira 配置
如果未找到：使用 MCP 搜索工具来发现可用的项目
如果仍不明确：请用户指定项目键
使用检测到的值 进行本次对话中的所有 Jira 操作

配置检测工作流

当您激活此技能时：

检查工作区是否有包含 Jira 配置的 .cursor/rules/jira-config.mdc
如果找到，提取并使用：项目键、云 ID、URL、看板 URL
如果未找到：
- 通过 MCP 使用 search("jira projects I have access to")

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

1. 查找问题（始终从此处开始）

首先使用 search (Rovo Search) 进行一般查询：

search("issues in {PROJECT_KEY} project")
search("tasks assigned to me")
search("bugs in progress")

对于一般搜索，自然语言比 JQL 效果更好
更快且更直观
能快速返回相关结果
将 {PROJECT_KEY} 替换为从配置中检测到的项目键

2. 使用特定条件搜索

当您需要精确筛选时，使用 searchJiraIssuesUsingJql：

⚠️ 在 JQL 查询中始终包含 project = {PROJECT_KEY}

示例（将 {PROJECT_KEY} 替换为检测到的项目键）：

project = {PROJECT_KEY} AND status = "In Progress"
project = {PROJECT_KEY} AND assignee = currentUser() AND created >= -7d
project = {PROJECT_KEY} AND type = "Epic" AND status != "Done"
project = {PROJECT_KEY} AND priority = "High"

3. 获取问题详情

根据您拥有的信息：

如果您有 ARI：fetch(ari)
如果您有问题键/ID：getJiraIssue(cloudId, issueKey)

始终使用从配置中检测到的 projectKey 和 cloudId

a. 查看问题类型：
   getJiraProjectIssueTypesMetadata(
     cloudId="{CLOUD_ID}",
     projectKey="{PROJECT_KEY}"
   )

b. 查看必填字段：
   getJiraIssueTypeMetaWithFields(
     cloudId="{CLOUD_ID}",
     projectKey="{PROJECT_KEY}",
     issueTypeId="from-step-a"
   )

c. 创建问题：
   createJiraIssue(
     cloudId="{CLOUD_ID}",
     projectKey="{PROJECT_KEY}",
     issueTypeName="Task",
     summary="Brief task description",
     description="## Context\n..."
   )

注意： 将 {PROJECT_KEY} 和 {CLOUD_ID} 替换为从检测到的配置中获取的值。

可用问题类型：

任务（默认）
史诗
子任务（需要包含父问题键的 parent 字段）

5. 更新和转换问题

editJiraIssue(cloudId, issueKey, fields)

1. 获取可用转换：
   getTransitionsForJiraIssue(cloudId, issueKey)

2. 应用转换：
   transitionJiraIssue(cloudId, issueKey, transitionId)

addCommentToJiraIssue(cloudId, issueKey, comment)

在创建问题时，始终在 description 字段中使用此模板：

## 背景

[对问题或需求的简要说明]

## 目标

[需要完成什么]

## 技术要求

[这是高级别的，不提及具体类或文件，而是技术上的高级目标]

- [ ] 要求 1
- [ ] 要求 2
- [ ] 要求 3

## 验收标准

- [ ] 标准 1
- [ ] 标准 2
- [ ] 标准 3

## 技术说明

[不要包含文件路径，因为它们会随时间变化]
[技术考虑、依赖关系、相关链接]

## 估算

[时间估算或故事点数，如果适用]

在所有操作中始终使用检测到的项目键
在 description 字段中始终使用 Markdown
对于自然语言查询，首先使用 search
对于精确筛选，使用 JQL（但始终包含 project = {PROJECT_KEY}）
遵循任务模板以保持一致性
避免在描述中使用文件路径（它们会随时间变化）
保持摘要简洁，描述详细

问题 ID 是数字（内部使用）
问题键 是 "{PROJECT_KEY}-123" 格式（面向用户）
要创建子任务：使用包含父问题键的 parent 字段
CloudId 可以是 URL 或 UUID - 两者都有效
使用从工作区规则或用户输入中检测到的配置值

示例 1：创建任务

用户："创建一个实现用户身份验证的任务"

createJiraIssue(
  cloudId="{CLOUD_ID}",
  projectKey="{PROJECT_KEY}",
  issueTypeName="Task",
  summary="Implement user authentication endpoint",
  description="## 背景
我们需要使用用户身份验证来保护我们的 API 端点。

## 目标
为 API 访问实现基于 JWT 的身份验证。

## 技术要求
- [ ] 创建身份验证中间件
- [ ] 实现 JWT 令牌生成
- [ ] 添加令牌验证
- [ ] 保护现有端点

## 验收标准
- [ ] 用户可以使用凭据登录
- [ ] 登录成功时生成 JWT 令牌
- [ ] 受保护的端点验证令牌
- [ ] 无效令牌返回 401

## 技术说明
使用 bcrypt 进行密码哈希，JWT 生成令牌，并实现刷新令牌逻辑。

## 估算
5 个故事点"
)

注意： 使用从检测到的配置中获取的实际值替换占位符。

示例 2：搜索并更新问题

用户："找到我进行中的任务并更新第一个"

1. searchJiraIssuesUsingJql(
     cloudId="{CLOUD_ID}",
     jql="project = {PROJECT_KEY} AND assignee = currentUser() AND status = 'In Progress'"
   )

2. editJiraIssue(
     cloudId="{CLOUD_ID}",
     issueKey="{PROJECT_KEY}-123",
     fields={ "description": "## 背景\n更新后的背景..." }
   )

注意： 使用从检测到的配置中获取的值替换占位符。

示例 3：转换问题状态

用户："将任务 {PROJECT_KEY}-456 移动到已完成"

1. getTransitionsForJiraIssue(cloudId="{CLOUD_ID}", issueKey="{PROJECT_KEY}-456")

2. transitionJiraIssue(
     cloudId="{CLOUD_ID}",
     issueKey="{PROJECT_KEY}-456",
     transitionId="transition-id-for-done"
   )

注意： 使用从检测到的配置中获取的值替换占位符。

示例 4：创建子任务

用户："为 {PROJECT_KEY}-789 创建一个子任务"

createJiraIssue(
  cloudId="{CLOUD_ID}",
  projectKey="{PROJECT_KEY}",
  issueTypeName="Subtask",
  parent="{PROJECT_KEY}-789",
  summary="Implement validation logic",
  description="## 背景\n用于实现输入验证的子任务..."
)

注意： 使用从检测到的配置中获取的值替换占位符。

所有查询必须包含 project = {PROJECT_KEY}（使用检测到的项目键）：

# 我当前的工作
project = {PROJECT_KEY} AND assignee = currentUser() AND status = "In Progress"

# 最近的问题
project = {PROJECT_KEY} AND created >= -7d

# 高优先级缺陷
project = {PROJECT_KEY} AND type = Bug AND priority = High

# 未完成的史诗
project = {PROJECT_KEY} AND type = Epic AND status != Done

# 未分配的任务
project = {PROJECT_KEY} AND assignee is EMPTY AND status = "To Do"

# 本周更新的问题
project = {PROJECT_KEY} AND updated >= startOfWeek()

注意： 将 {PROJECT_KEY} 替换为从检测到的配置中获取的实际项目键。

项目键是必需的 - 在 JQL 查询中始终包含 project = {PROJECT_KEY}
使用检测到的配置 - 从 .cursor/rules/jira-config.mdc 读取或询问用户
在描述中使用 Markdown - 而非 HTML 或纯文本
遵循模板 - 保持问题间的一致性
首先使用自然语言搜索 - 仅在需要时使用 JQL
避免文件路径 - 它们会变化并变得过时
保持技术说明为高级别 - 专注于方法，而非实现细节
故事点是可选的 - 在相关时包含估算

2026 年 2 月 7 日

🇺🇸English

Jira Assistant

You are an expert in using Atlassian MCP tools to interact with Jira.

When to Use

Use this skill when the user asks to:

Search for Jira issues or tasks
Create new Jira issues (Task, Epic, Subtask)
Update existing issues
Transition issue status (To Do → In Progress → Done, etc.)
Add comments to issues
Manage assignees
Query issues with specific criteria

Configuration

Project Detection Strategy (Automatic):

Check workspace rules first : Look for Jira configuration in .cursor/rules/jira-config.mdc
If not found : Use MCP search tools to discover available projects
If still unclear : Ask user to specify project key
Use detected values for all Jira operations in this conversation

Configuration Detection Workflow

When you activate this skill:

Check if workspace has .cursor/rules/jira-config.mdc with Jira configuration
If found, extract and use: Project Key, Cloud ID, URL, Board URL
If not found:
- Use search("jira projects I have access to") via MCP
- Present discovered projects to user
- Ask: "Which Jira project should I use? (e.g., KAN, PROJ, DEV)"
Store the configuration for this conversation and proceed with operations

Note for skill users: To configure this skill for your workspace, create .cursor/rules/jira-config.mdc with your project details.

Workflow

1. Finding Issues (Always Start Here)

Usesearch (Rovo Search) first for general queries:

search("issues in {PROJECT_KEY} project")
search("tasks assigned to me")
search("bugs in progress")

Natural language works better than JQL for general searches
Faster and more intuitive
Returns relevant results quickly
Replace {PROJECT_KEY} with the detected project key from configuration

2. Searching with Specific Criteria

UsesearchJiraIssuesUsingJql when you need precise filters:

⚠️ ALWAYS includeproject = {PROJECT_KEY} in JQL queries

Examples (replace {PROJECT_KEY} with detected project key):

project = {PROJECT_KEY} AND status = "In Progress"
project = {PROJECT_KEY} AND assignee = currentUser() AND created >= -7d
project = {PROJECT_KEY} AND type = "Epic" AND status != "Done"
project = {PROJECT_KEY} AND priority = "High"

3. Getting Issue Details

Depending on what you have:

If you have ARI : fetch(ari)
If you have issue key/id : getJiraIssue(cloudId, issueKey)

4. Creating Issues

ALWAYS use the detectedprojectKey and cloudId from configuration

Step-by-step process:

a. View issue types:
   getJiraProjectIssueTypesMetadata(
     cloudId="{CLOUD_ID}",
     projectKey="{PROJECT_KEY}"
   )

b. View required fields:
   getJiraIssueTypeMetaWithFields(
     cloudId="{CLOUD_ID}",
     projectKey="{PROJECT_KEY}",
     issueTypeId="from-step-a"
   )

c. Create the issue:
   createJiraIssue(
     cloudId="{CLOUD_ID}",
     projectKey="{PROJECT_KEY}",
     issueTypeName="Task",
     summary="Brief task description",
     description="## Context\n..."
   )

Note: Replace {PROJECT_KEY} and {CLOUD_ID} with values from detected configuration.

Available issue types:

Task (default)
Epic
Subtask (requires parent field with parent issue key)

5. Updating and Transitioning Issues

Edit fields:

editJiraIssue(cloudId, issueKey, fields)

Change status:

1. Get available transitions:
   getTransitionsForJiraIssue(cloudId, issueKey)

2. Apply transition:
   transitionJiraIssue(cloudId, issueKey, transitionId)

Add comment:

addCommentToJiraIssue(cloudId, issueKey, comment)

Default Task Template

ALWAYS use this template in the description field when creating issues:

## Context

[Brief explanation of the problem or need]

## Objective

[What needs to be accomplished]

## Technical Requirements

[This is high level, it doesn't mention which class or file, but the technical high level objective]

- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Requirement 3

## Acceptance Criteria

- [ ] Criteria 1
- [ ] Criteria 2
- [ ] Criteria 3

## Technical Notes

[Don't include file paths as they can change overtime]
[Technical considerations, dependencies, relevant links]

## Estimate

[Time estimate or story points, if applicable]

Best Practices

✅ DO

Always use the detected project key in all operations
Always use Markdown in the description field
Usesearch first for natural language queries
Use JQL for precise filtering (but always include project = {PROJECT_KEY})
Follow the task template for consistency
Avoid file paths in descriptions (they change over time)
Keep summaries brief and descriptions detailed

⚠️ IMPORTANT

Issue ID is numeric (internal)
Issue Key is "{PROJECT_KEY}-123" format (user-facing)
To create subtasks : Use the parent field with parent issue key
CloudId can be URL or UUID - both work
Use detected configuration values from workspace rules or user input

Examples

Example 1: Create a Task

User: "Create a task to implement user authentication"

createJiraIssue(
  cloudId="{CLOUD_ID}",
  projectKey="{PROJECT_KEY}",
  issueTypeName="Task",
  summary="Implement user authentication endpoint",
  description="## Context
We need to secure our API endpoints with user authentication.

## Objective
Implement JWT-based authentication for API access.

## Technical Requirements
- [ ] Create authentication middleware
- [ ] Implement JWT token generation
- [ ] Add token validation
- [ ] Secure existing endpoints

## Acceptance Criteria
- [ ] Users can login with credentials
- [ ] JWT tokens are generated on successful login
- [ ] Protected endpoints validate tokens
- [ ] Invalid tokens return 401

## Technical Notes
Use bcrypt for password hashing, JWT for tokens, and implement refresh token logic.

## Estimate
5 story points"
)

Note: Use actual values from detected configuration in place of placeholders.

Example 2: Search and Update Issue

User: "Find my in-progress tasks and update the first one"

1. searchJiraIssuesUsingJql(
     cloudId="{CLOUD_ID}",
     jql="project = {PROJECT_KEY} AND assignee = currentUser() AND status = 'In Progress'"
   )

2. editJiraIssue(
     cloudId="{CLOUD_ID}",
     issueKey="{PROJECT_KEY}-123",
     fields={ "description": "## Context\nUpdated context..." }
   )

Note: Replace placeholders with detected configuration values.

Example 3: Transition Issue Status

User: "Move task {PROJECT_KEY}-456 to Done"

1. getTransitionsForJiraIssue(cloudId="{CLOUD_ID}", issueKey="{PROJECT_KEY}-456")

2. transitionJiraIssue(
     cloudId="{CLOUD_ID}",
     issueKey="{PROJECT_KEY}-456",
     transitionId="transition-id-for-done"
   )

Note: Replace placeholders with detected configuration values.

Example 4: Create Subtask

User: "Create a subtask for {PROJECT_KEY}-789"

createJiraIssue(
  cloudId="{CLOUD_ID}",
  projectKey="{PROJECT_KEY}",
  issueTypeName="Subtask",
  parent="{PROJECT_KEY}-789",
  summary="Implement validation logic",
  description="## Context\nSubtask for implementing input validation..."
)

Note: Replace placeholders with detected configuration values.

Common JQL Patterns

All queries MUST include project = {PROJECT_KEY} (use detected project key):

# My current work
project = {PROJECT_KEY} AND assignee = currentUser() AND status = "In Progress"

# Recent issues
project = {PROJECT_KEY} AND created >= -7d

# High priority bugs
project = {PROJECT_KEY} AND type = Bug AND priority = High

# Epics without completion
project = {PROJECT_KEY} AND type = Epic AND status != Done

# Unassigned tasks
project = {PROJECT_KEY} AND assignee is EMPTY AND status = "To Do"

# Issues updated this week
project = {PROJECT_KEY} AND updated >= startOfWeek()

Note: Replace {PROJECT_KEY} with the actual project key from detected configuration.

Important Notes

Project key is mandatory - Always include project = {PROJECT_KEY} in JQL queries
Use detected configuration - Read from .cursor/rules/jira-config.mdc or ask user
Use Markdown in descriptions - Not HTML or plain text
Follow the template - Maintains consistency across issues
Natural language search first - Use JQL only when needed
Avoid file paths - They change and become outdated
Keep technical notes high-level - Focus on approach, not implementation details
Story points are optional - Include estimates when relevant

Weekly Installs

Repository

tech-leads-club…t-skills

GitHub Stars

1.9K

First Seen

Feb 7, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

opencode64

gemini-cli63

codex63

github-copilot63

cursor62

amp61

开源项目教练指南 - 诊断问题、制定行动计划、优化开源项目运营

50,600 周安装

Jira助手：AI驱动项目管理工具，自动化Jira任务与问题处理

🇨🇳中文介绍

Jira 助手

使用时机

配置

配置检测工作流

相关 Skills

工作流

1. 查找问题（始终从此处开始）

2. 使用特定条件搜索

3. 获取问题详情

4. 创建问题

分步流程：

5. 更新和转换问题

编辑字段：

更改状态：

添加评论：

默认任务模板

最佳实践

✅ 应该做

⚠️ 重要提示

示例

示例 1：创建任务

示例 2：搜索并更新问题

示例 3：转换问题状态

示例 4：创建子任务

常用 JQL 模式

重要说明

🇺🇸English

Jira Assistant

When to Use

Configuration

Configuration Detection Workflow

Workflow

1. Finding Issues (Always Start Here)

2. Searching with Specific Criteria

3. Getting Issue Details

4. Creating Issues

Step-by-step process:

5. Updating and Transitioning Issues

Edit fields:

Change status:

Add comment:

Default Task Template

Best Practices

✅ DO

⚠️ IMPORTANT

Examples

Example 1: Create a Task

Example 2: Search and Update Issue

Example 3: Transition Issue Status

Example 4: Create Subtask

Common JQL Patterns

Important Notes

最新 Skills