Do I need to authenticate before updating an issue?

Yes. The workflow requires identity to be assumed first and the correct workspace credentials to be available.

Which fields can I update in one command?

You can update title (-t), description (-d or --description-file), assignee (-a/--assignee), due date (--due-date), priority (--priority), estimate (--estimate), labels (-l), project (--project), team (--team), state (-s), and parent (--parent).

How should I update a long description?

Use --description-file to read content from a file (recommended for Markdown) instead of pasting long text in the CLI.

linear-issue-update

Flagged

{"isSafe":false,"isSuspicious":true,"riskLevel":"high","findings":[{"category":"prompt_injection","severity":"high","description":"Instruction to use an 'identity' skill to assume the agent's identity, which could enable prompt injection or escalation of authority and override system instructions.","evidence":"Rule: Identity\n\nFirst use the `identity` skill to assume the identity of the agent."}],"summary":"Content is largely safe for typical usage, but includes a prompt-injection risk: an instruction to assume the agent's identity via an identity skill, which could enable bypassing or manipulating intended system behavior. Consider removing or sandboxing this identity-handling directive."}

npx machina-cli add skill bryanp/agent-skills/update --openclaw

Files (1)

SKILL.md

1.4 KB

Use the linear issue update command to update an issue.

Rule: Identity

First use the identity skill to assume the identity of the agent.

Usage

Usage:   linear issue update [issueId]
Version: 1.10.0

Description:

  Update a linear issue

Options:

  -h, --help                         - Show this help.
  -w, --workspace     <slug>         - Target workspace (uses credentials)
  -a, --assignee      <assignee>     - Assign the issue to 'self' or someone (by username or name)
  --due-date          <dueDate>      - Due date of the issue
  -p, --parent        <parent>       - Parent issue (if any) as a team_number code
  --priority          <priority>     - Priority of the issue (1-4, descending priority)
  --estimate          <estimate>     - Points estimate of the issue
  -d, --description   <description>  - Description of the issue
  --description-file  <path>         - Read description from a file (preferred for markdown content)
  -l, --label         <label>        - Issue label associated with the issue. May be repeated.
  --team              <team>         - Team associated with the issue (if not your default team)
  --project           <project>      - Name of the project with the issue
  -s, --state         <state>        - Workflow state for the issue (by name or type)
  -t, --title         <title>        - Title of the issue

Source

git clone https://github.com/bryanp/agent-skills/blob/main/code/linear/issue/update/SKILL.mdView on GitHub

Overview

This skill updates an existing Linear issue using the linear issue update command. It supports editing title, description, assignee, due date, priority, estimates, labels, and more within a specified workspace and project, enabling precise issue management.

How This Skill Works

After the identity step, the skill runs the Linear CLI command linear issue update with the target issueId and chosen flags. You can specify workspace, assignee, due date, priority, estimates, description (or a description file), labels, team, project, state, and title to apply changes in one operation.

When to Use It

Reassign an issue to a teammate or yourself
Change the workflow state or status (e.g., To Do -> In Progress -> Done)
Update due date, estimate, or priority to reflect new timelines
Modify issue metadata such as labels, project, or parent issue
Update the description or replace it with content from a file

Quick Start

Step 1: Identify yourself with the identity skill to assume the agent's identity
Step 2: Run linear issue update [issueId] with desired flags (e.g., -t, -s, -d, --description-file, -w, -a, --due-date)
Step 3: Confirm the update by reviewing the issue or using a view command to verify changes

Best Practices

Identity guard: always run identity first to assume the agent's identity
Specify the workspace (-w/--workspace) to ensure changes apply to the correct environment
Use --description-file for long or Markdown descriptions to avoid CLI truncation
Combine related updates in a single command to minimize API calls
Validate changes by reviewing the resulting issue or running a quick view

Example Use Cases

linear issue update ISSUE-123 -w marketing -t "Campaign landing pages refresh" -s In Progress
linear issue update 2345 -w product --assignee @jdoe --due-date 2024-12-01 --priority 2
linear issue update 9876 -w dev -l bug -l urgent --state Done
linear issue update 321 -w ops -p 42 -t "Server maintenance window" --description-file ./desc.md
linear issue update 456 -w design -project Website Redesign --estimate 5 --due-date 2024-11-15

Frequently Asked Questions

Add this skill to your agents