transition-linear-issuelisted

# Transition a Linear Issue !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-context.sh` !`${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-context.sh transition-linear-issue` > **Configuration**: Set `work.integration: linear` in `.accelerator/config.md`. Move a Linear issue to a target WorkflowState via `issueUpdate`, resolving the state name to its team-scoped UUID **from the cached catalogue** — there is no live lookup. Work through the steps in order. This skill never auto-invokes. ## Step 1: Parse arguments Read the issue identifier and the target state name (both positional, e.g. `/transition-linear-issue BLA-123 "In Progress"`). ## Step 2: Preview (resolve from the catalogue) ``` ${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-transition-flow.sh \ <IDENTIFIER> "<STATE-NAME>" --describe ``` State matching is case-insensitive and trimmed. If the name is not in the catalogue (`E_TRANSITION_STATE_NOT_IN_CATALOGUE`) or is shared by two states (`E_TRANSITION_STATE_AMBIGUOUS`), STOP and report — suggest `/init-linear` to refresh, or ask the user to pick an unambiguous state. ## Step 3: Render the preview and confirm Show the resolved `stateId` and target state under: > **Proposed Linear write — review before sending** Ask: > Transition this issue? Reply **y** to confirm, **n** to revise, anything else > to abort. On a clear yes, proceed. On anything ambiguous, abort with "Aborted — no Linear write was made." ## Step 4: Send and render ``` ${CLAUDE