linear

Fetch a Linear issue by key and prepare a worktree for planning.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/rupertsworld/skills --skill linear-rupertsworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/rupertsworld/skills/tree/main/linear
Command: npx skills add https://github.com/rupertsworld/skills --skill linear-rupertsworld

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start work on a Linear issue by fetching the issue, creating a worktree on a conventionally-named branch, reading the project's must-read routing docs, then handing off to the code-plan skill for a structured planning dialogue ready for execution.

Core Features & Use Cases

  • Fetch a Linear issue by key (e.g., TEL-123) or search query, read details, and assemble context for planning.
  • Derive a conventional branch name and create or attach a worktree, then route to AGENTS.md/CLAUDE.md driven docs before planning.
  • Hand off to code-plan with the issue key to produce a concrete plan while keeping the session in the active worktree.

Quick Start

Say "/linear TEL-123" or provide an issue fragment to begin planning on that Linear issue.

Frequently Asked Questions about linear

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start working on a Linear issue with automated branch management?

To start working on a Linear issue, use an issue key like TEL-123 to fetch details, automatically create a conventional branch worktree, and route project docs for a structured planning dialogue.

What does automated issue tracking planning do before writing code?

Automated issue tracking planning fetches the Linear issue, reads repository routing docs like AGENTS.md and CLAUDE.md, and prepares a worktree to ensure the environment is ready for planning without starting implementation.

Can I search for a Linear issue by keyword instead of using the exact ticket ID?

Yes, you can provide an issue fragment or search query instead of an exact Linear key. The automation fetches the matching Linear issue, reads its context, and prepares a worktree on a conventional branch for planning.

Do I need AGENTS.md or CLAUDE.md files in my repository to use automated Linear worktree setup?

The automated Linear worktree setup reads must-read routing docs via AGENTS.md and CLAUDE.md to assemble project context. Having these files ensures the structured planning dialogue receives the correct repository guidelines.

Does automated Linear issue planning start writing code automatically after creating the branch?

No, automated Linear issue planning explicitly avoids starting implementation. It carries the Linear issue key into a structured planning dialogue via code-plan, keeping the session in the active worktree until the plan is fully defined.