Token导航 LogoToken导航

Agent Skill · 开发

jira-automation(Jira 自动化)

用于处理 Jira 项目、任务、缺陷、Sprint、负责人和状态流转。它适合让 Agent 辅助查询工单、汇总迭代进展、创建任务或整理需求和缺陷信息。使用时要确认项目权限、字段配置和工作流规则,不同团队的 Issue 类型、状态和必填字段可能不同;涉及批量改状态、改负责人或创建工单时,应先预览变更内容再执行。

jira-automation 是开发类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为操作浏览器;许可证信息还不明确,第三方扫描已通过,按安装量在开发类的 21,746 个 Skill 里排第 2,373。

总安装 17,682周安装 605GitHub Stars 89下载 8,011核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:jira-automation(Jira 自动化)
来源仓库:https://github.com/claude-office-skills/skills
仓库路径:skills/jira-automation
安装命令:
npx skills add https://github.com/claude-office-skills/skills --skill 'Jira Automation'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/claude-office-skills/skills --skill 'Jira Automation'

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

用于处理 Jira 项目、任务、缺陷、Sprint、负责人和状态流转,适合辅助查询工单、汇总迭代进展或创建任务。适用于自动化流程配置、规则引擎开发和 CI/CD 集成等开发类场景。支持按项目、状态、负责人等维度查询和整理工单信息。使用时需确认项目权限和工作流规则,批量操作前应预览变更内容。

jira-automation 属于开发类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/jira-automation

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/claude-office-skills/skills --skill 'Jira Auto…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要操作浏览器,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

jira-automation 怎么安装?

在终端执行 npx skills add https://github.com/claude-office-skills/skills --skill 'Jira Automation'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

jira-automation 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

jira-automation 需要什么权限?

权限级别是操作浏览器。该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

jira-automation 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

jira-automation 用的人多吗?

公开数据是累计安装 17,682 次,近一周安装 605 次,下载 8,011 次,GitHub 89 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

jira-automation 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理开发类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
skill-vetter

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
jira-automation

Jira 自动化 · 本页

17,68289操作浏览器未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Jira Automation

Comprehensive skill for automating Jira project management and agile workflows.

Core Workflows

1. Issue Management Pipeline

ISSUE LIFECYCLE:
┌─────────────────┐
│    Backlog      │
└────────┬────────┘
         ▼
┌─────────────────┐
│   To Do         │──────┐
└────────┬────────┘      │
         ▼               │
┌─────────────────┐      │ Blocked
│   In Progress   │◄─────┘
└────────┬────────┘
         ▼
┌─────────────────┐
│   In Review     │
└────────┬────────┘
         ▼
┌─────────────────┐
│     Done        │
└─────────────────┘

2. Automation Rules

automation_rules:
  - name: auto_assign_on_transition
    trigger:
      type: issue_transitioned
      to_status: "In Progress"
    condition:
      assignee: unassigned
    action:
      assign_to: trigger_user

  - name: add_label_on_priority
    trigger:
      type: issue_created
      priority: highest
    action:
      - add_label: "urgent"
      - send_slack: "#dev-alerts"

  - name: auto_close_subtasks
    trigger:
      type: issue_transitioned
      to_status: "Done"
      issue_type: Story
    action:
      transition_subtasks: "Done"

  - name: sla_warning
    trigger:
      type: scheduled
      cron: "0 9 * * 1-5"
    condition:
      jql: "status = 'In Progress' AND updated < -3d"
    action:
      - add_comment: "@assignee Please update this issue"
      - send_notification: assignee

Sprint Management

Sprint Planning Template

sprint_planning:
  name: "Sprint {{sprint_number}}"
  duration: 14  # days

  capacity_planning:
    team_size: 6
    hours_per_day: 6
    total_capacity: 504  # hours

  story_points:
    target: 42
    buffer: 10%  # for unplanned work

  ceremonies:
    - name: Sprint Planning
      day: 1
      duration: 2h
    - name: Daily Standup
      day: "daily"
      duration: 15m
    - name: Sprint Review
      day: 14
      duration: 1h
    - name: Retrospective
      day: 14
      duration: 1h

Sprint Board Configuration

board_config:
  type: scrum
  columns:
    - name: Backlog
      statuses: ["Backlog"]
    - name: To Do
      statuses: ["To Do", "Selected for Development"]
      wip_limit: null
    - name: In Progress
      statuses: ["In Progress"]
      wip_limit: 6
    - name: In Review
      statuses: ["Code Review", "QA"]
      wip_limit: 4
    - name: Done
      statuses: ["Done"]

  swimlanes:
    type: assignee
    show_epics: true

Issue Templates

Bug Report

bug_template:
  project: DEV
  issue_type: Bug
  fields:
    summary: "[BUG] {{title}}"
    description: |
      ## Description
      {{description}}

      ## Steps to Reproduce
      1. {{step1}}
      2. {{step2}}
      3. {{step3}}

      ## Expected Behavior
      {{expected}}

      ## Actual Behavior
      {{actual}}

      ## Environment
      - Browser: {{browser}}
      - OS: {{os}}
      - Version: {{app_version}}

      ## Screenshots
      {{attachments}}

    priority: {{severity}}
    labels: ["bug", "needs-triage"]
    components: ["{{component}}"]

Feature Request

feature_template:
  project: DEV
  issue_type: Story
  fields:
    summary: "[FEATURE] {{title}}"
    description: |
      ## User Story
      As a {{user_type}}, I want to {{action}} so that {{benefit}}.

      ## Acceptance Criteria
      - [ ] {{criteria1}}
      - [ ] {{criteria2}}
      - [ ] {{criteria3}}

      ## Technical Notes
      {{tech_notes}}

      ## Design Mockups
      {{mockups}}

    labels: ["feature", "needs-refinement"]
    story_points: null  # To be estimated

Epic Structure

epic_template:
  project: DEV
  issue_type: Epic
  fields:
    summary: "{{epic_name}}"
    description: |
      ## Overview
      {{overview}}

      ## Goals
      - {{goal1}}
      - {{goal2}}

      ## Success Metrics
      | Metric | Current | Target |
      |--------|---------|--------|
      | {{metric1}} | {{current1}} | {{target1}} |

      ## Timeline
      Start: {{start_date}}
      Target Completion: {{end_date}}

      ## Dependencies
      {{dependencies}}

    child_issues:
      - type: Story
        count: "auto"

JQL Queries Library

Common Queries

# My open issues
assignee = currentUser() AND resolution = Unresolved ORDER BY priority DESC

# Sprint progress
project = DEV AND Sprint = "Sprint 15" ORDER BY status

# Bugs by severity
project = DEV AND type = Bug AND resolution = Unresolved
ORDER BY priority DESC, created ASC

# Stale issues
project = DEV AND status = "In Progress" AND updated < -7d

# Ready for review
project = DEV AND status = "Code Review" AND "Code Reviewer" is EMPTY

# Release scope
fixVersion = "v2.5.0" AND resolution = Unresolved

# Team velocity
project = DEV AND type = Story AND Sprint in closedSprints()
AND resolved >= -90d

# Blockers
project = DEV AND (priority = Blocker OR labels = blocked)
AND resolution = Unresolved

Reporting & Dashboards

Sprint Dashboard

SPRINT 15 DASHBOARD
═══════════════════════════════════════

Progress:
Day 8 of 14 │ ████████░░░░░░ 57%

Story Points:
Committed: 42
Completed: 24  │ ████████████░░░░░░░░ 57%
Remaining: 18

Burndown:
│ 42 ┤ ▪
│    │  ▪▪
│    │    ▪▪
│    │      ▪▪▪
│ 21 ┤         ▪ ← Ideal
│    │          ▪▪
│    │            ▪▪
│    │              ▪▪
│  0 ┤                ▪
└────┴────────────────────
     Day 1           Day 14

Issue Status:
To Do        ███░░░░░░░ 6
In Progress  █████░░░░░ 8
In Review    ████░░░░░░ 5
Done         █████████░ 12

Velocity Chart

TEAM VELOCITY (Last 6 Sprints)
═══════════════════════════════════════

│  50 ┤
│     │           ▓▓
│  40 ┤    ▓▓     ▓▓     ▓▓     ▓▓
│     │    ▓▓ ▓▓  ▓▓     ▓▓ ▓▓  ▓▓
│  30 ┤ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│     │ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│  20 ┤ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│     │ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│  10 ┤ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│     │ ▓▓ ▓▓ ▓▓  ▓▓ ▓▓  ▓▓ ▓▓  ▓▓
│   0 ┴─────────────────────────────
       S10 S11 S12 S13 S14 S15

Average: 38 points | Trend: +5%

Integration Workflows

GitHub Integration

github_integration:
  branch_creation:
    trigger: issue_transitioned_to_in_progress
    pattern: "{{issue_type}}/{{issue_key}}-{{summary_slug}}"

  commit_linking:
    patterns:
      - "{{issue_key}}"
      - "#{{issue_key}}"
    action: add_comment_with_link

  pr_automation:
    on_pr_open:
      - transition_issue: "Code Review"
      - add_pr_link_to_issue
    on_pr_merge:
      - transition_issue: "Done"
      - add_comment: "Merged in {{pr_url}}"

Slack Integration

slack_integration:
  channels:
    dev_updates: "#dev-updates"
    alerts: "#dev-alerts"

  notifications:
    - event: blocker_created
      channel: alerts
      message: "🚨 Blocker: {{issue.key}} - {{issue.summary}}"

    - event: sprint_started
      channel: dev_updates
      message: "🏃 Sprint {{sprint.name}} has started! Goal: {{sprint.goal}}"

    - event: release_completed
      channel: dev_updates
      message: "🚀 Release {{version}} is live!"

Workflow Customization

Custom Workflow

workflow:
  name: Development Workflow
  statuses:
    - Backlog
    - Ready for Dev
    - In Progress
    - Code Review
    - QA
    - Ready for Release
    - Done

  transitions:
    - from: Backlog
      to: Ready for Dev
      name: "Refine"
      conditions:
        - story_points_set

    - from: Ready for Dev
      to: In Progress
      name: "Start Work"
      post_functions:
        - assign_to_current_user

    - from: In Progress
      to: Code Review
      name: "Submit for Review"
      validators:
        - has_linked_pr

    - from: Code Review
      to: QA
      name: "Pass Review"
      conditions:
        - all_reviewers_approved

    - from: QA
      to: Done
      name: "Pass QA"
      post_functions:
        - resolve_issue

Best Practices

  1. Keep Issues Small: Break down to complete in 1-2 days
  2. Write Clear Descriptions: Include all context needed
  3. Link Related Issues: Use proper issue linking
  4. Update Status Regularly: Move cards as work progresses
  5. Use Labels Consistently: Establish team conventions
  6. Estimate in Points: Use relative sizing
  7. Review Backlog Weekly: Keep backlog groomed

平台分布

Codex

35.64%
按下载量换算2,855

Claude

31.52%
按下载量换算2,525

Cursor

17.52%
按下载量换算1,404

Gemini CLI

8.9%
按下载量换算713

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

操作浏览器

该 Skill 可能涉及浏览器控制能力,使用时可能读取或操作网页内容,需要在受控环境中确认权限边界。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills