From routine
Fetches Jira ticket details via jira CLI: raw JSON, parsed dossier, comment summaries, attachment downloads, linked pull requests. Use when given Jira issue key.
npx claudepluginhub delexw/claude-code-miscThis skill is limited to using the following tools:
Fetch and display Jira ticket details using the `jira` CLI tool.
Views full Jira issue details using jirac CLI, including description, attachments, and metadata. Useful for viewing tickets via /View Issue or phrases like 'view PROJ-123'.
Manages Jira issues: view/create/update tickets, check sprints/backlogs via jira CLI, Atlassian MCP tools, or REST fallback. Activates on Jira keywords or issue keys like PROJ-123.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Fetch and display Jira ticket details using the jira CLI tool.
Raw arguments: $ARGUMENTS
Infer from the arguments:
.implement-assets/jira if not providedjira CLI installed and configured (https://github.com/ankitpokhrel/jira-cli)JIRA_API_TOKEN set with a valid Jira API token. Important: When checking this variable, verify at least 2 times before concluding it is not set. Environment variables can appear unset due to shell context differences. Never expose the value — use existence checks only (e.g. test -n "$JIRA_API_TOKEN").JIRA_SERVER set to the Jira base URL (e.g. https://yourcompany.atlassian.net).jira me to verify the CLI is installed and authenticated — if it fails, follow error handling in references/rules.md. Do NOT continue until jira me succeeds.mkdir -p OUT_DIR && jira issue view TICKET_KEY --raw > OUT_DIR/raw.json via Bashnode ${CLAUDE_SKILL_DIR}/scripts/parse-ticket.js < OUT_DIR/raw.json > OUT_DIR/dossier.json via Bash to get the parsed JSON outputnode ${CLAUDE_SKILL_DIR}/scripts/fetch-pull-requests.js < OUT_DIR/raw.json > OUT_DIR/pull-requests.json via Bash. If the output is a non-empty array, read OUT_DIR/dossier.json, add a pullRequests field with the array, and save back using the Write tool. PR fetch failure is non-fatal — warn and continue.comments array, analyze them following references/comment-rules.md. Replace the comments array in the JSON with a commentSummary object, then save the updated JSON back to OUT_DIR/dossier.json using the Write tool.attachments array, download them:
node ${CLAUDE_SKILL_DIR}/scripts/download-attachment.js --out OUT_DIR < OUT_DIR/raw.json via Bash