跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
浏览器与自动化

jira-issue-management

Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev).

jira-assistant-skills · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add grandcamel/JIRA-Assistant-Skills --skill jira-issue-management

技能说明


name: "jira-issue-management" description: "Core JIRA issue CRUD - create bugs/tasks/stories, get issue details, update fields, delete issues. TRIGGERS: 'show me [KEY]', 'get issue [KEY]', 'view issue', 'create a bug/task/story', 'update [KEY]', 'delete [KEY]', 'details of [KEY]', 'look up [KEY]', 'what's in [KEY]'. NOT FOR: epics (use jira-agile), transitions/status changes (use jira-lifecycle), comments/attachments (use jira-collaborate), time tracking (use jira-time), bulk operations on 10+ issues (use jira-bulk), dependencies/blockers (use jira-relationships), branch names/PR descriptions (use jira-dev)." version: "1.0.0" author: "jira-assistant-skills" license: "MIT" allowed-tools: ["Bash", "Read", "Glob", "Grep"]

jira-issue

Core CRUD operations for JIRA issues - create, read, update, and delete tickets.

Risk Levels

OperationRiskNotes
Get/view issue-Read-only
Create issue-Easily reversible (can delete)
Update fields!Can be undone via edit
Delete issue!!!PERMANENT — JIRA Cloud has no issue trash; a confirmation prompt is required
Delete with --force!!!PERMANENT, and skips the confirmation prompt

Risk Legend: - Safe, read-only | ! Caution, modifiable | !! Warning, destructive but recoverable | !!! Danger, irreversible

⚠️ PRIMARY USE CASE: Viewing Issue Details

This skill MUST be invoked when the user wants to see issue information.

CRITICAL: When user asks to view/show/get/see issue details, you MUST:

  1. Load this skill immediately (if not already loaded)
  2. Use the jira-as issue get command to retrieve the issue
  3. Display the full issue information to the user

Common phrases that REQUIRE invoking this skill:

  • "Show me [the issue/bug/task]" → Use jira-as issue get
  • "Get details of [issue]" → Use jira-as issue get
  • "View [the issue we created]" → Use jira-as issue get
  • "What's in [issue key]?" → Use jira-as issue get
  • "Display issue information" → Use jira-as issue get
  • "Look up [issue]" → Use jira-as issue get
  • "See [the bug]" → Use jira-as issue get
  • "Details of the bug/task/issue" → Use jira-as issue get

When to Use This Skill

Triggers: User asks to...

  • View/show/display/get/retrieve/see/check issue details ← Most common use case
  • Create a new JIRA issue (bug, task, story, epic)
  • Look up or examine an issue
  • Update issue fields (summary, description, priority, assignee, labels)
  • Delete an issue

Context awareness: If the user refers to "the issue/bug/task we just created" or uses pronouns like "it", resolve to the most recently created/mentioned issue in the conversation and retrieve its details.

Available Commands

This skill provides the following commands via the jira-as issue CLI:

  • jira-as issue create: Create new issues
  • jira-as issue get: Retrieve issue details
  • jira-as issue update: Modify issue fields
  • jira-as issue delete: Remove issues
  • jira-as issue transition: Transition an issue to a new status (alias for jira-as lifecycle transition)
  • jira-as issue transitions: List available transitions, read-only (alias for jira-as lifecycle transitions)
  • jira-as issue comment: Add a comment to an issue (alias for jira-as collaborate comment add)

All commands support --help for full option documentation.

Output Options

-o, --output [text|json] is available on issue get, issue create, and issue transitions. Other issue commands print plain-text output.

Templates

Pre-configured templates for common issue types:

  • bug_template.json - Bug report template
  • task_template.json - Task template
  • story_template.json - User story template

Use the --template option to apply a template during issue creation:

# Quick bug report using template
jira-as issue create --project PROJ --template bug --summary "Login page error"

# Quick task using template
jira-as issue create --project PROJ --template task --summary "Update documentation"

# Quick story using template
jira-as issue create --project PROJ --template story --summary "User can reset password"

Common Patterns

Create Issues

# Basic issue creation
jira-as issue create --project PROJ --type Bug --summary "Login fails on mobile"

# With description
jira-as issue create --project PROJ --type Bug --summary "Login fails on mobile" \
  --description "Users report 500 error when logging in from mobile browsers. See attached screenshot."

# With assignee (use 'self' for current user)
jira-as issue create --project PROJ --type Task --summary "Review PR #42" \
  --assignee self

# With agile fields
jira-as issue create --project PROJ --type Story --summary "User login" \
  --epic PROJ-100 --story-points 5

# With relationships and time estimate
jira-as issue create --project PROJ --type Task --summary "Setup database" \
  --blocks PROJ-123 --estimate "2d"

# With 'relates to' links
jira-as issue create --project PROJ --type Task --summary "Related feature" \
  --relates-to PROJ-456,PROJ-789

# With labels and components
jira-as issue create --project PROJ --type Task --summary "Setup CI pipeline" \
  --labels "backend,infrastructure" --components "Build,DevOps"

# With custom fields (JSON format)
jira-as issue create --project PROJ --type Bug --summary "Critical bug" \
  --custom-fields '{"customfield_10050": "production"}'

# Assign to sprint
jira-as issue create --project PROJ --type Story --summary "Feature X" \
  --sprint 42

# Create as a child of an epic or parent task
jira-as issue create --project PROJ --type Task --summary "Child task" \
  --parent PROJ-100

# For workflows that reject a parent at create time: create without the
# parent, then set it in a follow-up update
jira-as issue create --project PROJ --type Task --summary "Child task" \
  --parent PROJ-100 --parent-via-update

# Preview the payload that would be sent without creating the issue
ji
阅读完整来源 ↗