mcpField
J
jira-ticket-viewer

jira-ticket-viewer

github.com/delexwProductivity255 installsUpdated 31w ago
Repository

About jira-ticket-viewer

jira-ticket-viewer is a skill for fetching and presenting Jira issue details for people working with tickets through the jira CLI. It parses issue data, summarizes comments, and downloads attachments when present.

Key features

  1. 01Fetch raw issue data with the jira CLI
  2. 02Parse tickets into a JSON dossier
  3. 03Fetch and add associated pull requests
  4. 04Convert comments into a summary
  5. 05Download attachments and return their paths

Use cases

  1. 01View a Jira ticket as a structured dossier
  2. 02Summarize ticket comments for review
  3. 03Retrieve pull requests and attachments associated with a ticket

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/delexw/claude-code-misc --skill jira-ticket-viewer

After installing, type/jira-ticket-viewerin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

references/
comment-rules.md
output-format.md
rules.md
scripts/
download-attachment.js
fetch-pull-requests.js
parse-ticket.js

Details

From the project README

Jira Ticket Viewer

Fetch and display Jira ticket details using the jira CLI tool.

Inputs

Raw arguments: $ARGUMENTS

Infer from the arguments:

  • TICKET_KEY: the Jira issue key
  • OUT_DIR: output directory, or .implement-assets/jira if not provided

System Requirements

  • jira CLI installed and configured (https://github.com/ankitpokhrel/jira-cli)
  • Environment variable 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").
  • Environment variable JIRA_SERVER set to the Jira base URL (e.g. https://yourcompany.atlassian.net).

Execution

  1. Pre-flight check: Run 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.
  2. Validate TICKET_KEY against references/rules.md
  3. Fetch raw JSON (single API call): Run mkdir -p OUT_DIR && jira issue view TICKET_KEY --raw > OUT_DIR/raw.json via Bash
  4. Parse ticket: Run node ${CLAUDE_SKILL_DIR}/scripts/parse-ticket.js < OUT_DIR/raw.json > OUT_DIR/dossier.json via Bash to get the parsed JSON output
  5. Fetch pull requests: Run node ${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.
  6. Interpret comments: If the parsed JSON contains a non-empty 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.
  7. Attachments: If the parsed JSON contains a non-empty attachments array, download them:
    • Run node ${CLAUDE_SKILL_DIR}/scripts/download-attachment.js --out OUT_DIR < OUT_DIR/raw.json via Bash
    • Include downloaded attachment file paths in the output
  8. Return the parsed JSON output (see references/output-format.md for schema reference), including attachment download paths if any

Comments

Markdown supported