Jira integration for fetching issue context (Epics, Stories, Bugs) to enhance development workflows. Use for automatic issue detection, retrieving ticket details, acceptance criteria, and linked dependencies.
Retrieves Jira issue details via curl when issue keys are mentioned in conversation.
/plugin marketplace add resolve-io/.prism/plugin install prism-devtools@prismThis skill inherits all available tools. When active, it can use any tool Claude has access to.
README.mdreference/api-reference.mdreference/authentication.mdreference/error-handling.mdreference/extraction-format.mdProvides read-only Jira integration to enrich development workflows:
Automated context retrieval without leaving your workflow:
The skill uses curl via Bash tool to fetch Jira data:
curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
"https://resolvesys.atlassian.net/rest/api/3/issue/{issueKey}"
Why curl instead of WebFetch:
When user mentions issue key:
[A-Z]+-\d+Example workflow:
User: "jira PLAT-3213"
Agent executes:
curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
"https://resolvesys.atlassian.net/rest/api/3/issue/PLAT-3213"
Parses response and displays formatted issue details
Standard workflow:
[A-Z]+-\d+When user describes work without ticket:
User: "I need to implement the login feature"
Agent: "Great! Do you have a JIRA ticket number so I can get more context?"
User: "PLAT-456"
Agent: Fetches and displays issue details via curl
All Jira capabilities (when using this skill):
| Command | Purpose |
|---|---|
| Issue Retrieval | |
jira {issueKey} | Fetch and display full issue details |
jira-epic {epicKey} | Fetch epic and all child stories/tasks |
jira-search {jql} | Search issues using JQL query |
| Workflow Integration | |
auto-detect | Enable/disable automatic issue key detection |
ā API Reference
The skill automatically detects these patterns:
PLAT-123 (from core-config.yaml defaultProject)[A-Z]+-\d+ format (e.g., JIRA-456, DEV-789)Extract issue key from user message using regex:
[A-Z]+-\d+
Use Bash tool to execute curl command:
curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
"https://resolvesys.atlassian.net/rest/api/3/issue/{ISSUE_KEY}" \
2>&1
Critical points:
$JIRA_EMAIL and $JIRA_TOKEN environment variables-u flag for Basic Authentication-s for silent mode (no progress bar)2>&1 to catch errorsUse Python one-liner to extract key fields:
curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
"https://resolvesys.atlassian.net/rest/api/3/issue/PLAT-123" | \
python -c "
import json, sys
data = json.load(sys.stdin)
fields = data['fields']
print('Key:', data['key'])
print('Type:', fields['issuetype']['name'])
print('Summary:', fields['summary'])
print('Status:', fields['status']['name'])
print('Assignee:', fields.get('assignee', {}).get('displayName', 'Unassigned'))
"
Format the extracted data as structured markdown:
## š [{ISSUE_KEY}](https://resolvesys.atlassian.net/browse/{ISSUE_KEY})
**Type:** {Type} | **Status:** {Status} | **Priority:** {Priority}
**Assignee:** {Assignee} | **Reporter:** {Reporter}
### Description
{Description text}
### Acceptance Criteria
{Extracted AC or "Not specified"}
### Related Issues
- Blocks: {list}
- Blocked by: {list}
- Parent: [{PARENT}](link)
### Additional Context
- Labels: {labels}
- Components: {components}
- Updated: {date}
[View in Jira](https://resolvesys.atlassian.net/browse/{ISSUE_KEY})
When fetching issues, the skill extracts:
The Jira skill enhances other PRISM skills:
Configuration:
Credentials are configured via Windows environment variables:
JIRA_EMAIL=your.email@resolve.io
JIRA_TOKEN=your-jira-api-token
Core config reference (core-config.yaml):
jira:
enabled: true
baseUrl: https://resolvesys.atlassian.net
email: ${JIRA_EMAIL}
token: ${JIRA_TOKEN}
defaultProject: PLAT
Security Best Practices:
-u flagSetup:
JIRA_EMAIL = your Atlassian emailJIRA_TOKEN = your API tokenAuthentication Failed:
# Response: "Client must be authenticated to access this resource."
# Action: Verify JIRA_EMAIL and JIRA_TOKEN are set correctly
Issue Not Found (404):
# Response: {"errorMessages":["Issue does not exist or you do not have permission to see it."]}
# Action: Verify issue key spelling and user has permission
Network Error:
# Response: curl connection error
# Action: Check network connectivity and Jira availability
Graceful Degradation:
ā DO:
ā DON'T:
ā DO:
ā DON'T:
# Step 1: Fetch issue data
ISSUE_DATA=$(curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" \
"https://resolvesys.atlassian.net/rest/api/3/issue/PLAT-3213")
# Step 2: Check for errors
if echo "$ISSUE_DATA" | grep -q "errorMessages"; then
echo "Error fetching issue"
exit 1
fi
# Step 3: Extract and format
echo "$ISSUE_DATA" | python -c "
import json, sys
data = json.load(sys.stdin)
fields = data['fields']
print(f\"## š [{data['key']}](https://resolvesys.atlassian.net/browse/{data['key']})\")
print(f\"**Type:** {fields['issuetype']['name']} | **Status:** {fields['status']['name']}\")
print(f\"**Assignee:** {fields.get('assignee', {}).get('displayName', 'Unassigned')}\")
print(f\"\n### Summary\")
print(fields['summary'])
"
Core references (loaded as needed):
Shared references:
Q: Why use curl instead of WebFetch?
A: WebFetch doesn't support custom authentication headers needed for Jira API. curl with -u flag provides reliable Basic Authentication.
Q: Do I need to manually invoke this skill? A: No! The skill automatically activates when it detects Jira issue keys in conversation.
Q: Is this read-only? A: Yes. This integration only fetches data from Jira, it never creates or modifies issues.
Q: What if I don't have credentials configured? A: The skill gracefully degrades. It will inform you that Jira integration is unavailable and proceed without it.
Q: How do I verify credentials are working?
A: Test with: curl -s -u "$JIRA_EMAIL:$JIRA_TOKEN" "https://resolvesys.atlassian.net/rest/api/3/myself"
Q: Can I search for issues using JQL?
A: Yes! Use jira-search "project = PLAT AND type = Bug" to search using Jira Query Language.
This skill activates when you mention:
Skill Version: 1.1.0 Integration Type: Read-Only (curl + Bash) Icon: š« Last Updated: 2025-11-20 Method: curl via Bash tool with Basic Authentication
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.