show-linear-issue
Invocation: User- and model-invocable
Argument hint: <IDENTIFIER> [--comments N]
Allowed tools: Bash(${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/*), Bash(${CLAUDE_PLUGIN_ROOT}/scripts/config-*), Bash(jq), Bash(curl)
Source: skills/integrations/linear/show-linear-issue/SKILL.md
Show Linear Issue
Section titled “Show Linear Issue”!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh show-linear-issue
Configuration: Set
work.integration: linearin.accelerator/config.md. See the### worksection ofconfigure/SKILL.mdfor the full reference.
Fetch and render a single Linear issue by identifier.
Step 1: Resolve the identifier
Section titled “Step 1: Resolve the identifier”Read the issue identifier from the argument string (e.g. BLA-123). If none was
supplied, ask the user which issue to show.
Step 2: Fetch the issue
Section titled “Step 2: Fetch the issue”Run:
${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-show-flow.sh <IDENTIFIER> [--comments N]Run the bare path directly as an executable; never prefix it with
bash/sh/env (a wrapper prefix escapes the skill’s allowed-tools
permission and forces an unnecessary prompt).
An unknown identifier exits non-zero (E_SHOW_NOT_FOUND) — tell the user the
issue was not found.
Step 3: Render the issue
Section titled “Step 3: Render the issue”Render the issue’s fields under .data.issue:
- Identifier:
.identifier - Title:
.title - State:
.state.name - Assignee:
.assignee.name(orunassigned) - Description:
.description— already native Markdown, render it directly (no ADF conversion). - Comments: each
.comments.nodes[].body(Markdown), if any.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh show-linear-issue

