Use when the user mentions Jira issues (e.g., "PROJ-123"), asks about tickets, wants to create/view/update issues, check sprint status, or manage their Jira...
Real data. Real impact.
Emerging
Developers
Per week
Open source
Skills give you superpowers. Install in 30 seconds.
Natural language interaction with Jira. Supports multiple backends.
Run this check first to determine which backend to use:
1. Check if jira CLI is available: → Run: which jira → If found: USE CLI BACKEND
If no CLI, check for Atlassian MCP: → Look for mcp__atlassian__* tools → If available: USE MCP BACKEND
If neither available: → GUIDE USER TO SETUP
| Backend | When to Use | Reference |
|---|---|---|
| CLI | | |
| MCP | Atlassian MCP tools available | |
| None | Neither available | Guide to install CLI |
Skip this section if using MCP backend.
| Intent | Command |
|---|---|
| View issue | |
| List my issues | |
| My in-progress | |
| Create issue | |
| Move/transition | |
| Assign to me | |
| Unassign | |
| Add comment | |
| Open in browser | |
| Current sprint | |
| Who am I | |
Skip this section if using CLI backend.
| Intent | MCP Tool |
|---|---|
| Search issues | |
| View issue | |
| Create issue | |
| Update issue | |
| Get transitions | |
| Transition | |
| Add comment | |
| User lookup | |
| List projects | |
See
references/mcp.mdIssue keys follow the pattern:
[A-Z]+-[0-9]+When a user mentions an issue key in conversation:
jira issue view KEYjira open KEYmcp__atlassian__jira_get_issueCreating tickets:
Updating tickets:
Ask yourself:
What's the current state? — Always fetch the issue first. Don't assume status, assignee, or fields are what user thinks they are.
Who else is affected? — Check watchers, linked issues, parent epics. A "simple edit" might notify 10 people.
Is this reversible? — Transitions may have one-way gates. Some workflows require intermediate states. Description edits have no undo.
Do I have the right identifiers? — Issue keys, transition IDs, account IDs. Display names don't work for assignment (MCP).
NEVER transition without fetching current status — Workflows may require intermediate states. "To Do" → "Done" might fail silently if "In Progress" is required first.
NEVER assign using display name (MCP) — Only account IDs work. Always call
lookupJiraAccountIdNEVER edit description without showing original — Jira has no undo. User must see what they're replacing.
NEVER use
without all required fields (CLI) — Fails silently with cryptic errors. Check project's required fields first.--no-input
NEVER assume transition names are universal — "Done", "Closed", "Complete" vary by project. Always get available transitions first.
NEVER bulk-modify without explicit approval — Each ticket change notifies watchers. 10 edits = 10 notification storms.
If neither CLI nor MCP is available, guide the user:
To use Jira, you need one of:
jira CLI (recommended): https://github.com/ankitpokhrel/jira-cli
Install: brew install ankitpokhrel/jira-cli/jira-cli Setup: jira init
Atlassian MCP: Configure in your MCP settings with Atlassian credentials.
LOAD reference when:
Do NOT load reference for:
jira issue view KEY| Task | Load Reference? |
|---|---|
| View single issue | No |
| List my tickets | No |
| Create with description | Yes — CLI needs |
| Transition issue | Yes — need transition ID workflow |
| JQL search | Yes — for complex queries |
| Link issues | Yes — MCP limitation, need script |
References:
references/commands.mdreferences/mcp.mdNo automatic installation available. Please visit the source repository for installation instructions.
View Installation Instructions
1,500+ AI skills, agents & workflows. Install in 30 seconds. Part of the Torly.ai family.
© 2026 Torly.ai. All rights reserved.