smithery.ai

linear-update

Update a Linear issue's status, assignee, or labels. Use when the user says "update linear", "move issue", "close linear issue", or "assign issue".

First seen Mar 30, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash, Read, Write, Grep, Glob

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,627 B
  • docs SUMMARY.md 168 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

/linear-update — Update a Linear issue

Push updates to a Linear issue using schpet/linear-cli.

Steps

  1. Verify the Linear CLI is available:

``bash linear --version 2>/dev/null || echo "LINEARCLIMISSING" ``

  1. Parse $ARGUMENTS for the issue ID and field updates:

- First token: issue ID (e.g., ENG-123) - Remaining tokens: field=value pairs (e.g., status=done priority=high)

If no arguments, ask the user for the issue ID and what to update.

  1. Fetch the current issue state:

``bash linear issue view ENG-123 --json ``

  1. Show the proposed changes for confirmation:

``` ## Update: ENG-123 — <title>

Field Current New
Status In Progress Done
Priority Medium (3) High (2)

Apply these changes? ```

  1. Apply the update using linear issue update with the appropriate flags:

``bash linear issue update ENG-123 --state "Done" --priority 2 ``

Available flags (use linear issue update --help for full list): - --state "<state-name>" — set workflow state (e.g., "Todo", "In Progress", "Done") - --priority <number> — set priority (0=None, 1=Urgent, 2=High, 3=Medium, 4=Low) - --assignee "<username-or-email>" — assign to user (use @me for self) - --label "<label-name>" — add label (repeat flag for multiple) - -t "<title>" — update title - -d "<description>" — update description

  1. Report:

``` Updated: ENG-123 — <title> Changes: state → Done, priority → High

Run /linear-sync to update the local snapshot. ```

Arguments

  • $ARGUMENTS format: <issue-id> [state=<state>] [priority=<priority>] [assignee=<name>]
  • Examples:

- ENG-123 state=done — mark as done - ENG-123 priority=urgent assignee=@me — set priority and self-assign - ENG-123 label=bug label=regression — add labels

Notes

  • Always show current vs proposed state and confirm before applying
  • When marking an issue as Done, ask if a comment should be added (e.g., linking to the PR):

linear issue comment add ENG-123 -b "Fixed in PR #42"

  • Run /linear-sync after updates to refresh the local snapshot
  • If the issue doesn't exist in Linear, report the error clearly