linear-worktree

A command that creates a separate Git working directory for a Linear issue. Linear is a tool for tracking development work, while a Git worktree lets you work on another branch without changing the current directory.

In plain words
What is it for?
Use it to fetch an issue's suggested branch name, create its worktree from the main branch, copy selected configuration files, run setup, and switch into the new directory.
Why use it?
It removes the repetitive setup needed before starting an issue and keeps the issue's changes separate from the main working directory.

Command

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 commands/dgalarza/claude-code-workflows/linear-worktree
Clone the repo
git clone --depth 1 https://github.com/dgalarza/claude-code-workflows
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 905 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.00000 $0.00905
Opus 5 $0.00000 $0.00452
Sonnet 5 $0.00000 $0.00181
Haiku 4.5 $0.00000 $0.00090

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

Security

Grade A, and why

linear-worktree 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 2d 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.

plugins/rails-toolkit/commands/linear-worktree.md · 125 lines

How it starts

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

Linear Issue Worktree Setup

Set up a new git worktree for a Linear issue, creating a separate working directory off the main branch.

Usage

/linear-worktree <project-path> <linear-issue-id>

What this command does

  1. Fetch Linear Issue: Retrieves issue details to get the suggested git branch name
  2. Create Worktree: Creates a new git worktree in ../tracewell-<branch-name> directory
  3. Switch Context: Changes to the new worktree directory
  4. Ready for Work: Leaves you in the new worktree, ready to run /linear-implement

Arguments

  • First argument: Path to the project directory (e.g., tracewell2)
  • Second argument: The Linear issue ID (e.g., TRA-9, DEV-123)

Requirements

  • Linear integration configured (MCP Linear tools available)
  • Current working directory must be a git repository
  • main branch exists and is up-to-date

Example

/linear-worktree tracewell2 TRA-9

This will:

  1. Change to the tracewell2 directory
  2. Fetch Linear issue TRA-9 details
  3. Create a new worktree at ../tracewell-<branch-name>
  4. Copy .env and config/master.key to the new worktree
  5. Switch to the new worktree directory
  6. Run bin/setup inside the new worktree
  7. Ready for you to run /linear-implement TRA-9

Benefits of Using Worktrees

  • Work on multiple features simultaneously without branch switching
  • Keep your main working directory clean
  • Avoid stashing changes when switching between issues
  • Each worktree maintains its own file state

I'll help you set up a new git worktree for the Linear issue. Let me start by parsing the arguments and changing to the project directory.

Step 1: Navigate to Project Directory

First, I'll change to the specified project directory:

Project path: {first argument} Issue ID: {second argument}

Step 2: Fetch Linear Issue Details

I'll retrieve the issue information to get the suggested git branch name:

Let me fetch the complete issue details to determine the proper branch name for the worktree.

Read the full file on GitHub · 125 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. 2d ago First seen · 125 lines · 0 tokens per session scan A b3fe6f023f63

Subscribe to this mod's changes

linear-worktree is a command published in the GitHub repository dgalarza/claude-code-workflows (59 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 905 tokens. 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-30.