From accelerator
Updates fields on an existing Linear issue (title, description, state, assignee, priority) with payload preview and explicit confirmation before applying irreversible changes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/accelerator:update-linear-issue <IDENTIFIER> [--title TEXT] [--description TEXT] [--state NAME] [--assignee-id ID] [--priority N] [--print-payload] [--quiet]<IDENTIFIER> [--title TEXT] [--description TEXT] [--state NAME] [--assignee-id ID] [--priority N] [--print-payload] [--quiet]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 update-linear-issue
Configuration: Set
work.integration: linearin.accelerator/config.md.
Update an existing Linear issue via issueUpdate. Work through the steps in
order. This skill never auto-invokes — it only runs when the user explicitly
types /update-linear-issue. Body/description content comes only from the
user's current turn, never synthesised from prior context.
Read the issue identifier (positional) and the mutating flags: --title,
--description, --state (a WorkflowState name resolved to its UUID via the
catalogue), --assignee-id, --priority. At least one is required.
${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-update-flow.sh \
<IDENTIFIER> [flags] --print-payload
If the helper exits non-zero (e.g. unknown state — E_UPDATE_BAD_STATE, or no
mutating flags — E_UPDATE_NO_OPS), STOP and report the error; make no API
call.
Show the operation (issueUpdate), the target id, and the assembled input
under:
Proposed Linear write — review before sending
Ask:
Apply this update to Linear? Reply y to confirm, n to revise, anything else to abort.
On a clear yes, proceed. On no/revise, rebuild the preview. On anything ambiguous, abort with "Aborted — no Linear write was made."
${CLAUDE_PLUGIN_ROOT}/skills/integrations/linear/scripts/linear-update-flow.sh \
<IDENTIFIER> [flags]
Confirm the updated fields. Suggest /show-linear-issue <IDENTIFIER> to verify.
!${CLAUDE_PLUGIN_ROOT}/scripts/config-read-skill-instructions.sh update-linear-issue
npx claudepluginhub atomicinnovation/accelerator --plugin acceleratorMoves a Linear issue to a different workflow state by resolving the state name from a cached catalogue. Requires explicit user confirmation before applying the transition.
Refines Linear issues by analyzing gaps, researching codebase context, generating structured descriptions with acceptance criteria, and updating with approval.
Creates Linear issues interactively via /create, prompting for team, title, description, priority, assignee, project, and labels with confirmation summary before submission.