update-linear-issue

Solid

Use this skill only when the user explicitly invokes /update-linear-issue to change fields on an existing Linear issue (title, description, state, assignee, priority). This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It shows a payload preview, requires explicit confirmation, then applies the update.

Code & Development 34 stars 1 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 83/100

Stars 20%

Recency 20%

100

Frontmatter 20%

Documentation 15%

Issue Health 10%

License 10%

100

Description 5%

100

Skill Content

# Update Linear Issue !`accelerator config context --skill update-linear-issue --fail-safe` > **Configuration**: Set `work.integration: linear` in `.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. ## Step 1: Parse arguments 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. ## Step 2: Render the preview Show the resolved intent — the operation (`issueUpdate`), the target issue, and the fields being set (`--title`/`--description`/`--state`/`--assignee-id`/ `--priority`) �� under: > **Proposed Linear write — review before sending** At least one mutating flag is required; with none the subcommand refuses before any write (`E_UPDATE_NO_OPS`). A `--state` change resolves through the catalogue and is refused before any write if the name is unknown or ambiguous. ## Step 3: Confirm before writing 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." ## Step 4: Send an...

Details

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

Integrates with

Linear · Productivity

Bundled in these plugins

accelerator

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Solid

create-linear-issue

Use this skill only when the user explicitly invokes /create-linear-issue to create a new Linear issue from a local work-item file. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. It reads the work item's title and Markdown body, shows a payload preview, requires explicit confirmation, then creates the issue and writes the remote-allocated identifier (e.g. BLA-123) back into the file's external_id frontmatter field.

34 Updated yesterday

atomicinnovation

Code & Development Solid

transition-linear-issue

Use this skill only when the user explicitly invokes /transition-linear-issue to move an existing Linear issue to a different workflow state. This is a write skill with irreversible side effects — it must never be auto-invoked from conversational context. The target state name is resolved to its UUID from the cached catalogue (no live lookup). Shows a preview, requires explicit confirmation, then applies the transition.

34 Updated yesterday

atomicinnovation

Code & Development Listed

linear-issue-to-pr

Takes a Linear issue identifier (e.g. ENG-42) and carries it end to end in the current git repo - fetches the issue and its comments, creates or switches to the issue branch, implements the change, commits, pushes and opens a pull request (never merges). Use it whenever the user gives a Linear issue ID and wants it worked on, e.g. "get issue ENG-42", "work on ENG-42", "implement DBO-1104", "resuelve la issue ENG-42", "trabaja en ENG-42", or names a project together with an issue ID. Do not use it when the user only asks about an issue's status, wants to create or plan issues, or wants a summary without code changes.

1 Updated 3 days ago

mbarradev-debug