linear-update

A skill for updating Linear, a project-management system, with debugging findings and issue changes. It can add investigation comments and change issue status, labels, or priority when the required command-line access is available.

In plain words
What is it for?
Use it after debugging to record evidence and root causes, update an issue's status or priority, and add labels or comments to the relevant Linear issue.
Why use it?
It keeps the issue record aligned with what an investigation discovered. This prevents root causes, evidence, and follow-up decisions from remaining only in private notes.

Skill for Claude CodeCodex

Part of the workflows plugin — 29 skills, 5 commands, 17 agents shipped together

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.

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

Made for: Claude Code, Codex.

Or install workflows, the plugin that ships this one along with the rest of its 29 skills, 5 commands, 17 agents.

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,226 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00027 $0.01226
Opus 5 $0.00014 $0.00613
Sonnet 5 $0.00005 $0.00245
Haiku 4.5 $0.00003 $0.00123

Measured 3d ago against content hash a97347740190, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

linear-update 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 3d 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/linear-update/SKILL.md · 178 lines

How it starts

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

Update Linear Issue

Update Linear issues with debugging findings, status changes, and investigation notes.

When to Use

  • Adding debugging findings as comments
  • Updating issue status after investigation
  • Adding labels for categorization
  • Changing priority based on severity
  • Recording root cause analysis

Pre-flight Checks

Authentication

# Check linearis is available and authenticated
linearis --version 2>/dev/null || {
  echo "linearis CLI not installed"
  exit 1
}

linearis issues list --limit 1 >/dev/null 2>&1 || {
  echo "Not authenticated to Linear"
  exit 1
}

Common Commands

1. Add Comment

# Add single-line comment
linearis comments create ENG-1234 --body "Root cause identified: database connection pool exhausted"

# Add multi-line comment with heredoc
linearis comments create ENG-1234 --body "$(cat <<'EOF'
## Investigation Findings

**Root Cause**: Database connection pool exhausted

**Evidence**:
- GCP logs show "connection refused" errors starting at 10:30 UTC
- Kubernetes events show 1/3 pods in CrashLoopBackOff
- Pod describe shows max_connections reached

**Timeline**:
- 10:28 UTC: Traffic spike to 3x normal
- 10:30 UTC: First connection errors
- 10:32 UTC: Pod restarts begin

**Recommendation**: Increase database connection pool limit from 100 to 250
EOF
)"

2. Update Issue Status

# Change state to "In Progress"
linearis issues update ENG-1234 --state "In Progress"

# Change state to "Done"
linearis issues update ENG-1234 --state "Done"

# Common states: "Backlog", "Todo", "In Progress", "In Review", "Done", "Canceled"

3. Update Priority

# Set priority (1 = Urgent, 2 = High, 3 = Medium, 4 = Low)
linearis issues update ENG-1234 --priority 1

# Lower priority after resolution
linearis issues update ENG-1234 --priority 4

4. Add Labels

# Add labels (comma-separated)
linearis issues update ENG-1234 --labels "bug,production,database"

# Add labels (adding mode - default)
linearis issues update ENG-1234 --labels "investigating" --label-by adding

# Replace all labels (overwriting mode)
linearis issues update ENG-1234 --labels "resolved,production" --label-by overwriting

# Clear all labels
linearis issues update ENG-1234 --clear-labels

Read the full file on GitHub · 178 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. 3d ago First seen · 178 lines · 27 tokens per session scan A a97347740190

Subscribe to this mod's changes

linear-update is a skill published in the GitHub repository eveld/claude (10 stars, last pushed 7mo ago), licensed MIT. It adds 27 tokens to every session and 1,226 once invoked, about $0.0001 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

code-indexing-pipeline

How Infigraph turns source into a graph — adding a language (tree-sitter vs ANTLR grammar-plugin), cross-file call resolution, SCIP compiler-grade enrichment, and file-watch/reindex triage. Use when adding language support, debugging unresolved calls or SCIP import, or triaging stale index/watcher issues.

intuit/infigraph · 70 tokens

analysis-subsystems

How Infigraph's multi-repo/group mode and taint analysis work internally — HTTP contract extraction heuristics, cross-service edge linking, combined-graph merge, remote mode, plus taint's line-based tracking and sanitizer heuristic. Use when working on crates/infigraph-core/src/multi/ or src/taint/, or investigating…

intuit/infigraph · 80 tokens

review-pr-against-issue

Review one or more PRs against the GitHub issue(s) they claim to fix, including fetching PR branches directly when gh can't reach github.com (e.g. gh is authenticated to an enterprise host instead). Use whenever asked "does this PR fix issue.

intuit/infigraph · 61 tokens

golden-rss

Use when testing the rss golden build.

yusufkaraaslan/Skill_Seekers · 12 tokens

omh-buzz

This is a Hermes-native buzz workflow skill.

rlaope/oh-my-hermes · 95 tokens

redteam-api-detail-pack

Domain routing and boundary guidance for authorized API security testing, including BOLA/IDOR, authentication bypass, mass assignment, missing rate limits, and GraphQL issues. Use when a task belongs to the API testing domain and needs scope, evidence, pivot, or exit criteria.

Netw0rkNoob/VulnClaw · 61 tokens