update-linear-status

update-linear-status is a skill for Claude Code, Codex from jjxmonster/skills. It costs 58 tokens per session (655 once invoked), scanned A, original, MIT.

A workflow for changing the status of the active issue in Linear, a tool for tracking software tasks. It identifies the relevant ticket and moves it to a requested state.

In plain words
What is it for?
Use it to mark a coding task In Progress, Done, In Review, or Canceled. It can identify the issue from its ID, the conversation, or the current Git branch.
Why use it?
It removes the need to update the ticket manually while work begins, finishes, enters review, or is canceled. It also helps avoid changing the wrong issue.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to mark a coding task In Progress, Done, In Review, or Canceled. It can identify the issue from its ID, the conversation, or the current Git branch.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jjxmonster/skills/update-linear-status
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add jjxmonster/skills --skill update-linear-status
Clone the repo
git clone --depth 1 https://github.com/jjxmonster/skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for update-linear-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/jjxmonster/skills/update-linear-status/github.svg)](https://agentmods.dev/skills/jjxmonster/skills/update-linear-status)
Your own site
<a href="https://agentmods.dev/skills/jjxmonster/skills/update-linear-status"><img src="https://agentmods.dev/badge/skills/jjxmonster/skills/update-linear-status/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for update-linear-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/jjxmonster/skills/update-linear-status"><img src="https://agentmods.dev/badge/skills/jjxmonster/skills/update-linear-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 655 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00655
Opus 5 $0.00029 $0.00328
Sonnet 5 $0.00012 $0.00131
Haiku 4.5 $0.00006 $0.00065

Measured 9d ago against content hash 787ed3acfd4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

update-linear-status scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/update-linear-status/SKILL.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Update Linear Status

Update the active Linear issue for the current session using the Linear MCP server (plugin-linear-linear). Do not ask for confirmation unless the target issue or target status is ambiguous.

Identify the active issue

Resolve the issue ID in this order:

  1. Explicit ID in the user message or plan (e.g. PRJ-83, PRJ-81)
  2. Conversation context - the ticket being implemented, planned, or reviewed in this session
  3. Git branch - e.g. project/PRJ-83-... -> PRJ-83
  4. Ask the user only if none of the above apply

Update one issue: the leaf task the agent is doing, not the parent epic, unless the user explicitly names the epic.

Status transitions

When Set state to
Agent starts implementing a ticket In Progress
User asks to update Linear after completed work Done
User asks to send for review In Review
User cancels scope Canceled

When the user says "update the linear task" without a status, default to Done if the implementation is complete; otherwise use In Progress. Skip the update if the issue is already in the target state.

MCP workflow

Always read tool schemas first from the Linear MCP descriptors before calling.

  1. Fetch the current issue:
CallMcpTool:
  server: plugin-linear-linear
  toolName: get_issue
  arguments: { "id": "PRJ-83" }
  1. Update only the state:
CallMcpTool:
  server: plugin-linear-linear
  toolName: save_issue
  arguments: { "id": "PRJ-83", "state": "Done" }

Use the state name string (e.g. "Done"), not the internal ID. Common PRJnella states: Backlog, Todo, In Progress, In Review, Done, Canceled, Duplicate. If unsure or a state fails, call list_issue_statuses for team PRJnella.

  1. Verify with get_issue again. Confirm status / statusType matches the intended transition and report the issue URL to the user.

Rules

  • Do not update parent epics (e.g. PRJ-81) when completing a sub-task (e.g. PRJ-83).
  • Do not change assignee, priority, labels, or description unless the user asks.
  • Do not push git branches or link commits unless the user asks.
  • If Linear MCP is unavailable, tell the user which issue and status would have been set.

Read the full file on GitHub · 67 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 67 lines · 58 tokens per session scan A 787ed3acfd4b

Subscribe to this mod's changes

update-linear-status is a skill published in the GitHub repository jjxmonster/skills (8 stars, last pushed 20d ago), licensed MIT. It adds 58 tokens to every session and 655 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens