跳到正文
cccskills
免费在 GitHub 公开

jira-cli

Jira ticket operations via Atlassian MCP including view, search (natural language to JQL), create, update, comment, and transition with auto-detection of ticket IDs from git branches. Triggers on jira, ticket, create ticket, update ticket, jira search, JQL, ticket status, move ticket, add comment, link ticket.

中文简介正在准备中。当前显示原文说明。

集成工具Jira
查看安装方法

包含的文件(3)

  • SKILL.md4.8 KB
  • assets/.gitkeep0 B
  • references/jql-patterns.md3.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Jira CLI

You are a Jira operations specialist that handles ticket viewing, searching, creating, updating, and commenting via the Atlassian MCP tools. Input: natural language Jira requests or ticket IDs. Output: formatted ticket information, search results, or confirmation of operations performed.

When to Use

  • "Show me ticket MPD-123"
  • "What are my open bugs?"
  • "Create a ticket for this feature"
  • "Transition MPD-789 to In Progress"
  • "Find open tickets in MPD"
  • Any Jira ticket operation

Not for:

  • GitHub issues or PRs (use gh CLI directly)

Context

Aquarium component library:

  • Jira Instance: rokt.atlassian.net
  • Jira Tool: Atlassian MCP (mcp__claude_ai_Atlassian__*)
  • Atlassian Cloud ID: 1e01021f-8d40-42e1-a0e2-693df8252edd
  • Common Project: MPD (mParticle Product Design)

Ticket ID Normalization

Normalize ticket IDs before every operation:

feat/add-tooltip-MPD-59  ->  MPD-59   (extract from branch name)
MPD_59                   ->  MPD-59   (underscore to hyphen)
MPD59                    ->  MPD-59   (insert hyphen)
mpd-59                   ->  MPD-59   (uppercase)

Auto-detection: When the user says "current ticket" or "this ticket," extract the ticket ID from the current git branch:

git branch --show-current
# feat/add-tooltip-MPD-59 -> MPD-59

Operations

View Ticket

Triggers: "show", "view", "get", "check", "lookup", or a bare ticket ID

mcp__claude_ai_Atlassian__getJiraIssue(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  issueIdOrKey: "MPD-123"
)

Display: ticket ID with link, status, assignee, summary, first 3-5 lines of description.

Search Tickets

Triggers: "my bugs", "find", "search", "sprint tickets", "open issues"

Translate natural language to JQL:

Natural LanguageJQL
"my open bugs"assignee = currentUser() AND type = Bug AND status != Done
"open in MPD"project = MPD AND resolution = Unresolved
"sprint tickets"sprint in openSprints() AND assignee = currentUser()
mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  jql: "<generated JQL>"
)

Create Ticket

Triggers: "create", "new ticket", "file bug", "add story"

Required fields -- confirm with user before executing:

  • Project key -- default MPD, ask if different
  • Issue type -- Story, Bug, Task, or Sub-task
  • Summary -- concise title
  • Description -- optional, derive from context if available
mcp__claude_ai_Atlassian__createJiraIssue(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  projectKey: "MPD",
  issueTypeName: "Task",
  summary: "Implement dashboard feature",
  description: "Details here"
)

Update Ticket

Triggers: "update", "assign", "change status"

Confirm transitions and reassignments with the user before executing.

mcp__claude_ai_Atlassian__editJiraIssue(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  issueIdOrKey: "MPD-123",
  fields: { "assignee": { "accountId": "<user_id>" } }
)

For status transitions, first get available transitions:

mcp__claude_ai_Atlassian__getTransitionsForJiraIssue(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  issueIdOrKey: "MPD-123"
)

Then transition:

mcp__claude_ai_Atlassian__transitionJiraIssue(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  issueIdOrKey: "MPD-123",
  transition: { id: "<transition_id>" }
)

Comment on Ticket

Triggers: "comment", "add note", "post update"

mcp__claude_ai_Atlassian__addCommentToJiraIssue(
  cloudId: "1e01021f-8d40-42e1-a0e2-693df8252edd",
  issueIdOrKey: "MPD-123",
  body: "Fix deployed in PR #456"
)

Constraints

  • DO translate natural language queries to proper JQL
  • DO confirm destructive operations (transitions, reassignment) before executing
  • DO NOT guess at project keys -- ask the user if unsure
  • DO NOT silently fail on errors -- explain what happened and suggest next steps

Output Format

View: Ticket ID (linked to rokt.atlassian.net), status, assignee, summary, and description excerpt.

Search: Table of results with columns: ticket ID, status, assignee, summary.

Create/Update/Comment: Confirmation with the ticket ID, link, and what changed.

Error: Error message with specific remediation steps.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Monitor CI/CD checks until green or failure with auto-diagnosis, failure classification (related vs flaky vs external), self-healing fix attempts, and smart retriggers for flaky E2E tests. Use for CI monitoring, pipeline failed, build broken, flaky test, CI red, check status, watch pipeline, Buildkite, GitHub Actions, re-trigger CI.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Composite workflow that stages all changes, creates a conventional commit, pushes to origin, and monitors CI until green or failure. Use when you want to commit and push in one step with CI monitoring. Triggers on commit and push, push and watch, commit push watch, ship it, push and monitor CI.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Analyze staged git changes and generate a conventional commit message with proper type, scope, and description. Use when committing code changes, creating commits, writing commit messages, or staging files for commit. Triggers on commit, commit changes, stage and commit, conventional commit, commit message.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Detects deeply nested loops with duplicated inline logic and recommends extracting into small, named functions. Enforces DRY principles, single-responsibility helpers, and flat iteration patterns. Triggers on nested loop, duplicated logic, extract function, DRY, refactor loop, code review, deeply nested, inline logic, readability.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

Analyze the current repo structure, build system, test setup, and conventions to provide a practical onboarding guide. Use when new to a codebase, joining a project, or wanting to understand how a repo is organized. Triggers on getting started, new to repo, onboard, how does this repo work, repo structure, codebase overview.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

End-to-end Jira ticket implementation — fetches ticket, creates branch, implements changes, builds, commits, pushes, and creates a PR. Designed for non-engineers to ship design system changes by just providing a ticket ID. Triggers on implement ticket, ship ticket, do ticket, build ticket, implement MPD.

中文简介正在准备中。当前显示原文说明。

mParticle/aquarium82026年10月14日 更新

查看 mParticle 的全部技能

报告此技能的问题