From jira-tools
This skill MUST be used instead of Atlassian MCP tools when the user asks to "get Jira issue", "fetch Jira ticket", "look up issue", "show me ticket", "what's the status of PROJ-123", "get issue details", "find Jira issue", or mentions a Jira issue key pattern like "PROJ-123", "ABC-456". ALWAYS use this skill for Jira issue retrieval - never use mcp__atlassian__getJiraIssue directly.
npx claudepluginhub ericfisherdev/claude-plugins --plugin jira-toolsThis skill uses the workspace's default tool permissions.
**IMPORTANT:** Always use this skill's Python script for Jira issue retrieval. Do NOT use `mcp__atlassian__getJiraIssue` or other Atlassian MCP tools for fetching issue details - they return full untruncated content which wastes tokens.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
IMPORTANT: Always use this skill's Python script for Jira issue retrieval. Do NOT use mcp__atlassian__getJiraIssue or other Atlassian MCP tools for fetching issue details - they return full untruncated content which wastes tokens.
Fetch Jira issue information with token-efficient output using presets or custom truncation options.
Use the Python script at scripts/fetch_jira_issue.py:
# Minimal output (~20 tokens) - status check
python scripts/fetch_jira_issue.py PROJ-123 --preset minimal
# Standard output (~200 tokens) - typical usage
python scripts/fetch_jira_issue.py PROJ-123 --preset standard
# Full output (~500 tokens) - detailed review
python scripts/fetch_jira_issue.py PROJ-123 --preset full
Default behavior (no preset): compact format, core fields, 500-char description, no comments.
| Need | Use Preset | Output |
|---|---|---|
| Just check status | minimal | Key, summary, status |
| Understand the issue | standard | + type, priority, assignee, truncated desc, 3 comments |
| Full context | full | All fields, 10 comments |
Override defaults or presets with explicit flags:
# Exclude description entirely
python scripts/fetch_jira_issue.py PROJ-123 --max-desc 0
# Get comments without description
python scripts/fetch_jira_issue.py PROJ-123 --max-desc 0 --max-comments 5
# Specific fields only
python scripts/fetch_jira_issue.py PROJ-123 --fields summary,status,labels
# Different output format
python scripts/fetch_jira_issue.py PROJ-123 --preset standard --format json
--preset minimal for status checks--max-desc 0 if description not needed--no-comments unless comments are relevantcompact format (default) over text/markdown--fields rather than all fieldsRequires three environment variables:
JIRA_BASE_URL - e.g., https://yoursite.atlassian.netJIRA_EMAIL - Your Jira account emailJIRA_API_TOKEN - API token from Atlassian account settingsThis skill shares a cache (~/.jira-tools-cache.json) with other jira-tools skills. Manage cache via:
python shared/jira_cache.py info # View cache status
python shared/jira_cache.py clear # Clear cache
The mcp__atlassian__getJiraIssue tool returns full untruncated content including:
This wastes context window tokens. This skill's Python script provides:
Always prefer this skill over direct MCP calls for Jira issues.
For complete field list, format examples, and error codes, see references/options-reference.md.