# Jira Issue Summary

> Full context for one Jira issue: fields, comments, worklogs, changelog, and links, as one document. Use for "summarize PAY-123" or "what's the status of PAY-123".

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

---


# Jira: Issue Summary

Read-only. Run from this skill's directory:

```bash
python3 ../jira/scripts/jira_tool.py issue_summary --issue_key PAY-123 [--sections issue,worklogs]
```

(First-time setup, once per environment: `pip install -r ../jira/requirements.txt`.)

`--issue_key` is required. Prints one JSON document combining fields,
comments, worklogs, changelog, and links. Never invent or fabricate
issue data -- produce a concise natural-language summary of status,
recent activity, and any linked work, using only what the JSON returned.

`--sections` (optional, comma-separated subset of `issue`, `comments`,
`worklogs`, `changelog`, `linked_issues`) limits what's fetched and
returned -- omit it for everything, or narrow it (e.g. `--sections issue`
for just current fields) when the question doesn't need the full
history, to save tokens.

If the result contains `"error"`, tell the user what went wrong in
plain language (not found, permission denied, etc.) instead of
retrying silently or fabricating a result.

See `../jira/README.md` for architecture details and the full
environment-variable table.