Agent skill

Fetch Jira Issue

by openshift-eng in openshift-eng/ai-helpers

Fetch JIRA issue details including status, assignee, comments, and progress classification

Apache-2.0Auto-check passed

Install Fetch Jira Issue

skills CLI

$ npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install openshift-eng/ai-helpers fetch-jira-issue --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ci/skills/fetch-jira-issue .claude/skills/fetch-jira-issue && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "fetch-jira-issue" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue into .claude/skills/fetch-jira-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-jira-issue", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install openshift-eng/ai-helpers fetch-jira-issue --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ci/skills/fetch-jira-issue .agents/skills/fetch-jira-issue && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "fetch-jira-issue" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue into .agents/skills/fetch-jira-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-jira-issue", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install openshift-eng/ai-helpers fetch-jira-issue --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ci/skills/fetch-jira-issue .cursor/skills/fetch-jira-issue && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "fetch-jira-issue" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue into .cursor/skills/fetch-jira-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-jira-issue", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/openshift-eng/ai-helpers.git --path plugins/ci/skills/fetch-jira-issue

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install openshift-eng/ai-helpers fetch-jira-issue --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ci/skills/fetch-jira-issue .gemini/skills/fetch-jira-issue && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "fetch-jira-issue" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue into .gemini/skills/fetch-jira-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-jira-issue", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install openshift-eng/ai-helpers fetch-jira-issue

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ci/skills/fetch-jira-issue .github/skills/fetch-jira-issue && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "fetch-jira-issue" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue into .github/skills/fetch-jira-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-jira-issue", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install openshift-eng/ai-helpers fetch-jira-issue --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ci/skills/fetch-jira-issue .opencode/skills/fetch-jira-issue && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "fetch-jira-issue" agent skill from https://github.com/openshift-eng/ai-helpers/tree/main/plugins/ci/skills/fetch-jira-issue into .opencode/skills/fetch-jira-issue/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-jira-issue", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: fetch-jira-issue
GitHub stars: 120
Token cost: ~1.7k tokens
SKILL.md length: 418 words
Files: 3
Skills in repo: 118
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Fetch JIRA issue details including status, assignee, comments, and progress classification

Works in 3 steps: Run the Python Script → Parse the Output → Use Progress Classification
SKILL.md covers When to Use This Skill, Prerequisites, Implementation Steps and Error Handling, plus 3 more sections
Runs Python scripts from its folder; calls python3, jq and curl; reaches github.com and redhat.atlassian.net; needs JIRA_API_TOKEN

What it does

Fetch Jira Issue is an agent skill from openshift-eng/ai-helpers. Fetch JIRA issue details including status, assignee, comments, and progress classification

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `README.md` and `fetch_jira_issue.py`).

It works with Jira and Python. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

Example prompts

“/fetch-jira-issue”

Requirements

Python 3
A credential in JIRA_API_TOKEN

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Run the Python Script
Parse the Output
Use Progress Classification

What it can do on your machine

Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships script files (Python), which the agent can run.
Shell commands in SKILL.md call:
- python3
- jq
- curl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
- redhat.atlassian.net
Also links to:
- id.atlassian.com
- developer.atlassian.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
- JIRA_API_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fetch Jira Issue loads about 1.7k tokens when it runs. Until then it costs about 27 tokens; SKILL.md has 418 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~27
When it runs · the whole SKILL.md, loaded when a task matches: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 418 words, ~1,747 tokens.

Download SKILL.mdSave it as .claude/skills/fetch-jira-issue/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: fetch-jira-issue
description: Fetch JIRA issue details including status, assignee, comments, and progress classification

Fetch JIRA Issue

This skill fetches detailed information about a JIRA issue from the Red Hat JIRA REST API. It retrieves status, assignee, priority, resolution, comments, linked PRs, and classifies the issue's progress as ACTIVE, STALLED, or NEEDS_ATTENTION.

When to Use This Skill

Use this skill when you need to:

Check the status and progress of a JIRA bug linked to a regression triage
Determine if a bug is being actively worked on or needs attention
Extract PR links from JIRA comments
Get assignee and component information for a JIRA issue
Analyze recent comment activity on a bug

Prerequisites

JIRA API Token: Required for authentication
- Set environment variable: export JIRA_API_TOKEN="your-token"
- Set environment variable: export JIRA_USERNAME="your-atlassian-email"
- Obtain from: https://id.atlassian.com/manage-profile/security/api-tokens
- Alternatively, pass --token TOKEN and --username USERNAME on the command line
Network Access: Must be able to reach redhat.atlassian.net
- Check: curl -s -o /dev/null -w '%{http_code}' https://redhat.atlassian.net
Python 3: Python 3.6 or later
- Check: python3 --version
- Uses only standard library (no external dependencies)

Implementation Steps

Step 1: Run the Python Script

bash

# Path to the Python script
script_path="plugins/ci/skills/fetch-jira-issue/fetch_jira_issue.py"

# Fetch issue data in JSON format (default)
python3 "$script_path" OCPBUGS-74401 --format json

# Or fetch as human-readable summary
python3 "$script_path" OCPBUGS-74401 --format summary

# Pass token explicitly instead of using JIRA_API_TOKEN env var
python3 "$script_path" OCPBUGS-74401 --token "your-token" --format json

Step 2: Parse the Output

The script outputs structured JSON data that can be further processed:

bash

# Store result in variable
jira_data=$(python3 "$script_path" OCPBUGS-74401 --format json)

# Extract key fields
status=$(echo "$jira_data" | jq -r '.status')
assignee=$(echo "$jira_data" | jq -r '.assignee.display_name // "Unassigned"')
progress_level=$(echo "$jira_data" | jq -r '.progress.level')
progress_reason=$(echo "$jira_data" | jq -r '.progress.reason')

# Check progress classification
echo "Status: $status"
echo "Assignee: $assignee"
echo "Progress: $progress_level - $progress_reason"

Step 3: Use Progress Classification

The skill automatically classifies issue progress:

ACTIVE: Issue is being worked on (assigned with recent activity, PRs linked, or active status)
STALLED: Issue is assigned but has no activity in 14+ days
NEEDS_ATTENTION: Issue is NEW/unassigned or has no progress
RESOLVED: Issue is closed/verified

bash

# Example: Check if a triaged regression's bug needs attention
progress_level=$(echo "$jira_data" | jq -r '.progress.level')

case "$progress_level" in
  "ACTIVE")
    echo "Bug is being worked on - no action needed"
    ;;
  "STALLED")
    echo "Bug may need attention - consider commenting or reassigning"
    ;;
  "NEEDS_ATTENTION")
    echo "Bug needs someone to pick it up"
    ;;
  "RESOLVED")
    echo "Bug is closed"
    ;;
esac

Show full SKILL.md (181 more words)Show less

Error Handling

The script exits with code 1 and prints errors to stderr for these cases:

No token: JIRA_API_TOKEN not set and --token not provided
Auth failure (401): Token is invalid or expired
Access denied (403): Token lacks permissions for the project
Not found (404): Issue key doesn't exist
Network error: Cannot reach redhat.atlassian.net

bash

# Example: Handle missing token gracefully
if [ -z "$JIRA_API_TOKEN" ] || [ -z "$JIRA_USERNAME" ]; then
  echo "Warning: JIRA_API_TOKEN or JIRA_USERNAME not set. Skipping JIRA analysis."
else
  jira_data=$(python3 "$script_path" "$jira_key" --format json 2>/dev/null)
  if [ $? -ne 0 ]; then
    echo "Warning: Failed to fetch JIRA issue. Continuing without JIRA data."
  fi
fi

Output Format

JSON Format (--format json)

json

{
  "key": "OCPBUGS-74401",
  "url": "https://redhat.atlassian.net/browse/OCPBUGS-74401",
  "summary": "ovn-ipsec-host creates duplicate openssl attribute",
  "status": "Modified",
  "resolution": null,
  "priority": "Critical",
  "assignee": {
    "display_name": "Jane Developer",
    "email": "jdeveloper@redhat.com"
  },
  "reporter": {
    "display_name": "John Reporter",
    "email": "jreporter@redhat.com"
  },
  "components": ["Networking / cluster-network-operator"],
  "labels": ["Regression"],
  "fix_versions": ["4.22"],
  "created": "2026-01-20T14:30:00.000+0000",
  "updated": "2026-02-10T09:15:00.000+0000",
  "comment_count": 5,
  "comments": [
    {
      "author": "Jane Developer",
      "created": "2026-02-08T10:00:00.000+0000",
      "body": "PR submitted: https://github.com/openshift/ovn-kubernetes/pull/1234"
    }
  ],
  "linked_prs": [
    "https://github.com/openshift/ovn-kubernetes/pull/1234"
  ],
  "progress": {
    "level": "ACTIVE",
    "label": "ACTIVE",
    "reason": "PR in progress (1 linked)",
    "days_since_update": 2,
    "days_since_last_comment": 4
  }
}

Summary Format (--format summary)

JIRA Issue: OCPBUGS-74401
============================================================

Summary: ovn-ipsec-host creates duplicate openssl attribute
URL: https://redhat.atlassian.net/browse/OCPBUGS-74401
Status: Modified
Priority: Critical

Assignee: Jane Developer
Reporter: John Reporter

Components: Networking / cluster-network-operator
Labels: Regression
Fix Versions: 4.22

Created: 2026-01-20
Updated: 2026-02-10

Progress: ACTIVE - PR in progress (1 linked)
  Days since update: 2
  Days since last comment: 4

Linked PRs (1):
  - https://github.com/openshift/ovn-kubernetes/pull/1234

Recent Comments (1 of 5 total):
  [2026-02-08] Jane Developer:
    PR submitted: https://github.com/openshift/ovn-kubernetes/pull/1234

Notes

The script uses only Python standard library modules (no pip dependencies)
All comments are returned in the JSON output; the summary format shows only the last 3
PR links are extracted from comment bodies using pattern matching for GitHub PR URLs
Progress classification uses configurable thresholds: 7 days for "recent", 14 days for "stale"
The --token flag takes precedence over the JIRA_API_TOKEN environment variable

Files

SKILL.md and 2 other files in plugins/ci/skills/fetch-jira-issue of openshift-eng/ai-helpers.

SKILL.md
README.md
fetch_jira_issue.py

Open the folder on GitHubat commit a627176

Compare with similar skills

Fetch Jira Issue next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fetch Jira Issue compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Fetch Jira Issue this skillopenshift-eng/ai-helpers	120	—	~1.7k	Automated safety check: Pass	Apache-2.0	2 days ago
Rota Check Periodic Jobsoracle/graalpython	1.7k	—	~792	Automated safety check: Pass	Custom licence	yesterday
Kanban TuiZaloog/kanban-tui	285	—	~4.1k	Automated safety check: Pass	MIT	1 mo ago
GitHub PR Mirrororacle/graalpython	1.7k	—	~1.3k	Automated safety check: Pass	Custom licence	yesterday
Atlassian Readonly Skillssillsdev/FieldWorks	110	—	~1.3k	Automated safety check: Pass	Custom licence	yesterday
Atlassian Skillssillsdev/FieldWorks	110	—	~2.7k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Rota Check Periodic Jobs
oracle/graalpython
Official
Analyze current GraalPy periodic job failures for ROTA. An agent skill from oracle/graalpython.
1.7k GitHub stars~792 tokensUpdated yesterday
Testing & QAAuto-check passed
Kanban Tui
Zaloog/kanban-tui
Comprehensive kanban board and task management via ktui CLI.
285 GitHub stars~4.1k tokensUpdated 1 mo ago
Productivity & AutomationAuto-check passed
GitHub PR Mirror
oracle/graalpython
Official
Mirror an external GitHub pull request into the internal GraalPython Bitbucket review flow, including OCA label checks, Jira creation or reuse, preserving PR commits, pre-commit cleanup, and handoff…
1.7k GitHub stars~1.3k tokensUpdated yesterday
Auto-check passed
Atlassian Readonly Skills
sillsdev/FieldWorks
Read-only Python utilities for Jira (SIL Data Center): fetch an issue, search with JQL, read transitions, links, worklogs, agile boards and projects.
110 GitHub stars~1.3k tokensUpdated yesterday
Auto-check passed
Atlassian Skills
sillsdev/FieldWorks
Python utilities for Jira (SIL Data Center) covering issue management, JQL search, workflows and transitions, links, agile boards, worklogs and projects.
110 GitHub stars~2.7k tokensUpdated yesterday
Auto-check passed
Scrum Master
alirezarezvani/claude-skills
Advanced Scrum Master skill for data-driven agile team analysis and coaching.
28k GitHub starsUsed in 1 repo~2.4k tokens
Product & Project ManagementAuto-check passed

Questions about Fetch Jira Issue

What does Fetch Jira Issue do?

Fetch JIRA issue details including status, assignee, comments, and progress classification. Fetch Jira Issue is an agent skill from openshift-eng/ai-helpers.

How do I install Fetch Jira Issue in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a claude-code`. Or copy the skill folder (plugins/ci/skills/fetch-jira-issue in openshift-eng/ai-helpers) into .claude/skills/fetch-jira-issue in your project. Claude Code loads it when a task matches its description.

How do I install Fetch Jira Issue in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a codex`. Or copy the skill folder (plugins/ci/skills/fetch-jira-issue in openshift-eng/ai-helpers) into .agents/skills/fetch-jira-issue in your project. Codex loads it when a task matches its description.

Can I use Fetch Jira Issue in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill fetch-jira-issue -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fetch-jira-issue, .gemini/skills/fetch-jira-issue, .github/skills/fetch-jira-issue and .opencode/skills/fetch-jira-issue in your project.

What does Fetch Jira Issue need to run?

Going by SKILL.md and its folder, Fetch Jira Issue needs Python for the scripts in its folder, the command-line tools its instructions call (python3, jq and curl) and credentials named JIRA_API_TOKEN. Our summary lists: Python 3; A credential in JIRA_API_TOKEN.

Does Fetch Jira Issue access the network?

SKILL.md names 4 domains. In commands or code: github.com and redhat.atlassian.net; the agent is likely to contact these when it follows the instructions. As links in the text: id.atlassian.com and developer.atlassian.com. This is read from the text; nothing was executed.

Is Fetch Jira Issue safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fetch Jira Issue use?

Fetch Jira Issue is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fetch Jira Issue use?

About 1.7k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Fetch Jira Issue?

Skills that share tags, products or a category with Fetch Jira Issue: Rota Check Periodic Jobs (oracle/graalpython, 1.7k stars), Kanban Tui (Zaloog/kanban-tui, 285 stars), GitHub PR Mirror (oracle/graalpython, 1.7k stars) and Atlassian Readonly Skills (sillsdev/FieldWorks, 110 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fetch Jira Issue?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Fetch Jira Issue

Facts

At a glance

What it does

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Fetch JIRA Issue

When to Use This Skill

Prerequisites

Implementation Steps

Step 1: Run the Python Script

Step 2: Parse the Output

Step 3: Use Progress Classification

Error Handling

Output Format

JSON Format (--format json)

Summary Format (--format summary)

Notes

See Also

Files

Compare with similar skills

Similar skills

More from openshift-eng/ai-helpers

Related

Questions about Fetch Jira Issue