What is fetch_jira_requirements?

A Jira retrieval command that reads requirements, user stories, or issues from Jira and saves them as Markdown or JSON files.

It helps fetch one Jira issue, issues from a project and type, results matching a JQL query, or child issues of an epic.

It removes the need to copy ticket details by hand when preparing documentation or test automation.

How anhtester/claude-testing-kit configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to anhtester/claude-testing-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/anhtester/claude-testing-kit/main/.claude/commands/fetch_jira_requirements.md

Clone the repo

git clone --depth 1 https://github.com/anhtester/claude-testing-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/fetch_jira_requirements/github.svg)](https://agentmods.dev/commands/anhtester/claude-testing-kit/fetch_jira_requirements)

Your own site

<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/fetch_jira_requirements"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/fetch_jira_requirements/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/anhtester/claude-testing-kit/fetch_jira_requirements"><img src="https://agentmods.dev/badge/commands/anhtester/claude-testing-kit/fetch_jira_requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 770 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00770
Opus 5.5	$0.00007	$0.00308
Sonnet 5.5	$0.00003	$0.00154
Haiku 4.5	$0.00002	$0.00077

Measured 1mo ago against content hash 458ccf855c99, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fetch_jira_requirements scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

fetch_jira_requirements — 89% identical, 8 lines differ

.claude/commands/fetch_jira_requirements.md · 61 lines

How it starts

The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow: Fetch Jira Requirements

BẮT BUỘC (MANDATORY SKILL): Bạn PHẢI nạp và đọc kỹ nội dung của skill skills-jira-integration (tại .claude/skills/skills-jira-integration/SKILL.md) để biết cách sử dụng scripts trước khi bắt đầu.

Workflow này giúp lấy requirements, user stories, hoặc issues từ Jira và chuyển thành tài liệu phục vụ test automation.

Các bước thực hiện:

Kiểm tra prerequisites:
- Đọc skill skills-jira-integration để nắm cấu trúc scripts.
- Kiểm tra file .env đã tồn tại và được cấu hình đúng.
- Kiểm tra dependencies đã được cài đặt (scripts/integrations/node_modules/).
- Nếu chưa cài, chạy: cd scripts/integrations && npm install
Xác định thông tin cần lấy:
- Hỏi user cung cấp thông tin:
  - Issue key cụ thể (VD: PROJ-123) → dùng --issue
  - Project key + Issue type (VD: PROJ, Story) → dùng --project --type
  - JQL query tùy chỉnh → dùng --jql
  - Epic key (lấy children) → dùng --epic
- Xác định format output: json (default) hoặc md (markdown requirement)

Thực thi script:

Chạy lệnh phù hợp:

# Lấy 1 issue cụ thể
node scripts/integrations/jira/jira_fetcher.js --issue <ISSUE_KEY>

# Lấy issues theo project
node scripts/integrations/jira/jira_fetcher.js --project <PROJECT_KEY> --type <TYPE> --max <N>

# Tìm theo JQL
node scripts/integrations/jira/jira_fetcher.js --jql "<JQL_QUERY>"

# Xuất Markdown
node scripts/integrations/jira/jira_fetcher.js --issue <KEY> --format md --output ./requirements/jira

Xử lý kết quả:
- Kiểm tra output file được tạo trong requirements/jira/ (hoặc --output chỉ định).
- Nếu format json: Đọc và hiển thị tóm tắt issues cho user.
- Nếu format md: Hiển thị nội dung markdown requirement cho user review.
- Nếu gặp lỗi: Đọc log, phân tích nguyên nhân theo bảng Troubleshooting trong skill.
Xử lý lỗi thường gặp:
- HTTP 401: Token sai → hướng dẫn user kiểm tra JIRA_API_TOKEN hoặc JIRA_PAT
- HTTP 404: Issue không tồn tại hoặc JIRA_BASE_URL sai
- File .env not found: Hướng dẫn user copy .env.example → .env
- Module not found: Chạy npm install trong scripts/integrations/

Read the full file on GitHub · 61 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 61 lines · 17 tokens per session scan A 458ccf855c99

Subscribe to this mod's changes

fetch_jira_requirements is a command published in the GitHub repository anhtester/claude-testing-kit (61 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 770 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code Project management aitesting anhtester claudetestingkit test-automation test-manual

claude-testing-kit: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Workflow: Fetch Jira Requirements

Các bước thực hiện:

What this file has done since we first saw it

Other commands, from other repositories

workspace

brd-interviewer

template

fest-show

sync-linear

workpm