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.
Best use case
jira-cli is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using jira-cli should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/jira-cli/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How jira-cli Compares
| Feature / Agent | jira-cli | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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:
```bash
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 Language | JQL |
| ---------------- | ------------------------------------------------------------ |
| "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.Related Skills
jira-ticket-start
Start work on a Jira ticket by fetching ticket details, creating a properly named feature branch, and beginning codebase investigation. Use when starting a new ticket, beginning work on a Jira issue, or picking up a task from the backlog. Triggers on start ticket, begin work, pick up ticket, start jira, new ticket work, PROJ-123.
skill-tour
Interactive guided tour of all available AI coding skills with live demos. Walks through headline capabilities, offers try-it-now demos, discovers repo-specific tools, and provides a cheat sheet reference. Triggers on what can you do, show skills, skill tour, available tools, capabilities, what skills.
publish-branch
Push current branch to remote origin and generate PR title and description from branch name and commit history. Use when publishing a branch, creating a PR, pushing to remote, or preparing PR content. Triggers on publish branch, push branch, create PR, open pull request, push and PR.
pr
Create a pull request from the current branch. Triggers on create PR/open PR/make PR/submit PR/push PR/raise PR/open a pull request/create a pull request/ready to merge/branch is ready when the user wants to turn their current branch into a GitHub pull request with a well-structured description
pr-review-handler
Monitor PR review comments and automatically classify and address reviewer feedback including code changes, questions, and nits. Use when handling PR reviews, addressing reviewer comments, responding to code review feedback, or automating review resolution. Triggers on handle reviews, PR review, address feedback, reviewer comments, code review, review response.
implement-ticket
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.
getting-started
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.
dry-code-reviewer
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.
conventional-commit
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.
commit-push-watch
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.
ci-watcher
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.
add-rokt-icons
Add Rokt/Untitled UI icons to the Aquarium library. Accepts a Figma URL, icon names, or a screenshot — figures out what's needed, registers icons, verifies build, and optionally creates a PR. Designed for designers. Triggers on add rokt icon, rokt icon, untitled ui icon, register rokt, add icons from figma.