# Jira Release Reader

> Read one Jira version and extract content relevant to a research context. Returns ~500 token summary.

- Skill: `jimweller/jira-release-reader` (Agent Skill)
- Install (CLI): `npx skillmds@latest add jimweller/jira-release-reader`
- Raw SKILL.md: https://api.skillmd.com/api/skills/jimweller/jira-release-reader/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Research & Search
- Author: jimweller (https://skillmd.com/u/jimweller)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/jimweller/jira-release-reader

---



# Jira Release Reader

You read ONE Jira version and extract content relevant to the research context (~500 tokens).

## Loading the Script

The jira-api.sh script is at:
```
~/.dataops-assistant/bin/jira-api.sh
```

## Input Format

The user provides: `{project} {version_name} | {research context}`

Examples:
- `PE 2025.1.0 | looking for what features shipped in this release`
- `ML 2024.3.0 | understanding bug fixes related to authentication`
- `DATA 1.5.0 | finding who contributed to this version`

## Instructions

1. Extract project, version name, and research context from input
2. Get version details:
   ```bash
   bash ~/.dataops-assistant/bin/jira-api.sh version-get <project> "<version_name>"
   ```
3. Query issues in this version (load tool first with ToolSearch):
   ```
   mcp__atlassian__searchJiraIssuesUsingJql(
     jql: "project = <project> AND fixVersion = \"<version_name>\"",
     limit: 50
   )
   ```
4. Read the research context - it tells you WHAT to extract
5. Extract ONLY information relevant to that context
6. Return structured output with relevance rating

**Key principle**: You are NOT summarizing everything. You extract what matters for THIS research question.

## Output Format

```
VERSION: [Project] [Version Name]
STATUS: [released/unreleased] | RELEASE DATE: [date or "Not set"]
DESCRIPTION: [First 200 chars of description if present]

RESEARCH CONTEXT: [echo back the research context]

RELEVANT FINDINGS:
- [Finding directly relevant to research context]
- [Finding directly relevant to research context]

ISSUES IN VERSION: [count]
- [Key]: [Summary] (if relevant)
- [Key]: [Summary] (if relevant)
[... up to 10 most relevant]

ISSUE TYPES BREAKDOWN:
- Stories: X
- Bugs: Y
- Tasks: Z

RELEVANCE: [high|medium|low] - [one sentence explanation]
```

## Rules

- MAX ~500 tokens output
- Focus on research context - extract what's RELEVANT, not everything
- If version has minimal relevance, say so and keep output brief
- Limit issues list to 10 most relevant entries
- Include type breakdown only if relevant to research question

## Relevance Guide

- **high**: Version directly answers the research question with specific information
- **medium**: Version contains useful related information but doesn't fully answer
- **low**: Version is tangentially related or only touches the topic briefly