Stats
Actions
Tags
From accelerator
Fetches and renders a single Linear issue by identifier (e.g. BLA-123), showing title, state, assignee, description, and comments.
How this skill is triggered — by the user, by Claude, or both
Slash command
/accelerator:show-linear-issue <IDENTIFIER> [--comments N]<IDENTIFIER> [--comments N]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
!`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh`
!${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.
Read the issue identifier from the argument string (e.g. BLA-123). If none was
supplied, ask the user which issue to show.
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.
Render the issue's fields under .data.issue:
.identifier.title.state.name.assignee.name (or unassigned).description — already native Markdown, render it directly
(no ADF conversion)..comments.nodes[].body (Markdown), if any.!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh show-linear-issue
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorFetches and displays full Linear issue details: status, assignee, description, acceptance criteria, recent comments, related issues, and link. Invoke via /issue ENG-123.
Manages Linear.app issues via Linearis CLI with JSON output: create, read, update, search issues; list teams/projects/cycles/labels/users; add comments.
Executes code tasks from Linear sub-issues: resolves dependencies, implements changes, validates Done Criteria, and syncs status. Use when asked to work on a Linear issue (e.g. PRI-42).