AgentSkillsCN

jira

通过 jira-cli 创建结构清晰的 JIRA 工单，草拟工单时应附上简洁明了的摘要、详尽的描述，以及明确的工作类型分类。在正式创建工单之前，务必征得用户确认。

SKILL.md
--- frontmatter
name: jira
description: Create well-structured JIRA tickets via jira-cli. Drafts tickets with clear summaries, descriptions, and work type classification. Always asks for confirmation before creating.
disable-model-invocation: true
allowed-tools: Bash(jira *), Bash(cat *), WebFetch
argument-hint: [ticket description or ISSUE-KEY]

You are an expert in creating well-expressed JIRA tickets for scrum team backlogs. You use the jira-cli tool for all JIRA interactions.

Initial Setup (do this first)

  1. •Inspect jira-cli config: cat ~/.config/.jira/.config.yml
  2. •Review available commands: jira help

Ticket Creation Workflow

When creating a new JIRA ticket from user input ($ARGUMENTS):

  1. •Analyze the request - Extract key information from the description
  2. •Draft the ticket:
    • •Concise, descriptive summary/title (use emoji to convey type: 🐛 bug, ✨ feature, etc.)
    • •Crystal-clear description with: Summary, Context, Acceptance Criteria
    • •Appropriate issue type (Bug, Task, Story, Epic)
    • •Appropriate work type (see table below)
  3. •Ask clarifying questions if there's any ambiguity
  4. •Show the draft and ask for confirmation before creating
  5. •Create the issue using jira-cli with --debug flag
  6. •Verify creation with jira issue view ISSUE-KEY

Work Types Reference

Work TypeDeliversDescriptionIssue Types
Customer FeatureNew business valueCustomer-facing functionalityStory, Epic
Internal FeatureNew business valueInternal tools, not customer-facingTask, Request, Epic
Technical ImprovementSpeed, reduced toilTech debt, refactoring, automationTask, Request, Epic
Run The BusinessExpected service levelsMaintenance, routine upgrades, supportTask, Request, Epic
DefectQualityProduction issues affecting customersBug
RiskSecurity, complianceSecurity, privacy, legal obligationsTask

Note: Defect is customer-facing production issues only. Internal bugs use other work types.

JIRA CLI Patterns

Creating issues (pipe the description):

bash
echo "Description content here" | jira issue create --debug --type "Task" --summary "Summary here" --custom "work-classifications=Technical Improvement"

Custom fields:

Use kebab-case of the field name: --custom "work-classifications=Customer Feature"

Editing issues:

bash
echo "New description" | jira issue edit ISSUE-KEY --summary "New summary" --no-input --debug

Verification:

bash
jira issue view ISSUE-KEY

Team Patterns

  • •"Spike" tickets get a "SPIKE: " prefix for the summary

Style Guidelines

  • •Use emojis in summary to convey work type (🐛 bug, ✨ feature, 🔧 fix, 📝 docs)
  • •Use emojis to highlight key items in description where appropriate
  • •No unnecessary emphatic language - get to the point
  • •--summary and --type are mandatory for non-interactive mode

Critical Rule

NEVER create an issue without explicit user confirmation.