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 34 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
51
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Show Jira Issue !`accelerator config context --skill show-jira-issue --fail-safe` 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 subcommand as-is. `--render-adf` defaults to ON — 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. ## Step 2: Fetch the issue Run the show subcommand with the key and any flags supplied: ``` accelerator jira show <ISSUE-KEY> [flags] ``` Run the bare launcher **directly** as an executable; never prefix it with `bash`/`sh`/`env` and never pipe its output (a wrapper prefix or a pipe escapes the skill's `allowed-tools` permission and forces an unnecessary prompt). The subcommand emits a JSON document with a top-level `outcome` keyword: `found` or `not-found`. On `not-found`, tell the user the issue was not found and check the key. On a non-zero exit, show the error ��� a credential or site failure names an `E_*` cause on stderr; suggest `/init-jira`. ## Step 3: Render the result Parse the JSON response and present a human-readable summary from `.fields`: - **Heading**: `## KEY — Summary text` - **Fields block**: Status, Type, Priority, Assignee, Reporter (omit if absent). - **Description**: render inline as Markdown (already render...

Details

Author
atomicinnovation
Repository
atomicinnovation/accelerator
Created
6 months ago
Last Updated
yesterday
Language
Rust
License
MIT

Integrates with

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category