show-jira-issue

Solid

Use this skill when the user asks about a specific Jira issue by key (e.g. PROJ-123, ENG-456) — for viewing the description, status, comments, transitions, or any other field. Trigger when the user says 'look up', 'check on', 'tell me about', 'what's on', or 'what is the status of' a key, or asks any direct question about an issue they reference. Do NOT trigger when an issue key appears incidentally inside other prose (commit messages, code review comments, release notes), where the user is talking about the issue rather than asking to fetch it.

Code & Development 19 stars 1 forks Updated today MIT

Install

View on GitHub

Quality Score: 87/100

Stars 20%
43
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Show Jira Issue !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh show-jira-issue` Fetch and render a single Jira issue by key. Work through the steps below in order. ## Step 1: Parse the issue key and flags The first positional argument is the issue key (e.g. `ENG-42`, `PROJ-1234`). Remaining arguments are passed through to the helper as-is. `--render-adf` defaults to ON at the helper layer — single-issue reads are for humans, so rendered Markdown is the natural output. Pass `--no-render-adf` verbatim if the user explicitly asked for raw ADF or JSON. The SKILL does not invert the default; the default lives in the helper where it is testable and consistent with running the helper directly. ## Step 2: Run the helper Invoke `jira-show-flow.sh` with the key and any flags supplied: ``` ${CLAUDE_PLUGIN_ROOT}/skills/integrations/jira/scripts/jira-show-flow.sh \ <ISSUE-KEY> [flags] ``` If the exit code is non-zero, show the error to the user: - Exit 80 (`E_SHOW_NO_KEY`): no issue key was supplied — ask the user for one. - Exit 81 (`E_SHOW_BAD_COMMENTS_LIMIT`): `--comments` was out of range [0, 100]. Explain the constraint. - Exit 82 (`E_SHOW_BAD_FLAG`): unrecognised flag. Show the usage banner from the helper's stderr. - Any `jira-request.sh` exit (11–23): show the error and suggest checking credentials with `/init-jira`. ## Step 3: Render the result Parse the JSON response and present a human-r...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
2 months ago
Last Updated
today
Language
HTML
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Data & Documents Solid

search-jira-issues

Use this skill whenever the user wants to search, list, or filter Jira tickets — by assignee, status, label, project, type, component, reporter, parent, or free text — even if they say 'find', 'show me', 'what's open', 'list my tickets', or similar phrasing rather than 'search Jira'. Composes safe JQL from structured flags, executes a paginated search against a Jira Cloud tenant, and renders a summary table of the results. Supports --render-adf to convert ADF descriptions to Markdown inline. Prefer this skill over raw JQL whenever the user's intent maps to a structured flag.

19 Updated today
atomicinnovation
Data & Documents Listed

jira

This skill should be used when the user mentions a Jira ticket key (e.g. SOX-1234, DEVTOOLS-456), asks about ticket details, or wants to look up a Jira issue. Fetches live ticket data from Jira Cloud.

0 Updated 1 months ago
toh995
Code & Development Solid

create-jira-issue

Use this skill only when the user explicitly invokes /create-jira-issue to create a new Jira issue. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. Accepts a project key, issue type, summary, optional Markdown body, and optional fields (assignee, priority, labels, components, parent, custom fields). Converts the body to ADF, shows a payload preview, requires explicit confirmation, then POSTs to Jira and returns the new issue key.

19 Updated today
atomicinnovation