command

linear-task-to-issue — Claude Code command

Q: How do I install linear-task-to-issue in Claude Code?

Run `npx claude-code-templates@latest --command sync/linear-task-to-issue`. The command file lands at `.claude/commands/linear-task-to-issue.md`.

Q: What does the command need to run?

An authenticated `gh` CLI and access to the Linear task. Use `--skip-attachments` to leave out the attachment step when the files are not reachable.

A slash command that turns a Linear task into a GitHub issue, carrying over fields, links, attachments and comments. Useful when planning lives in Linear and code lives in GitHub.

Install into Claude Code · claude-code-templates All methods and platforms ↓

npx claude-code-templates@latest --command sync/linear-task-to-issue

Open on GitHub

What linear-task-to-issue does

Point the command at a Linear task and it builds the matching issue in your current repository. It pulls the task data first, then assembles the issue body, maps Linear fields onto GitHub ones, and sets labels, assignees and milestone. Parent-child links, team context and project associations come along too.

Attachments are downloaded from Linear and uploaded to GitHub, with references in the text rewritten. Comments arrive with their authors and original dates, and user mentions are translated through a mapping of Linear emails to GitHub usernames. At the end the command writes cross-references on both sides and records the result in a sync database.

It drives gh, so an authenticated GitHub CLI is a prerequisite — otherwise the repository lookup fails. Attachment migration also needs working access to the Linear files; when those links are locked down, pass --skip-attachments and leave that step out. Arguments pick the target: [task-id], --repo, --milestone, --close-linear, --skip-attachments.

What it helps with

move a Linear task into GitHub without retyping every field
keep parent and child task links intact during the move
carry attachments over and fix the references to them
import comments with authors and timestamps
set up cross-references between Linear and GitHub

Example prompts for the agent

Convert LIN-482 into an issue in this repo
Move LIN-482 to GitHub with milestone v2.1
Convert LIN-482 and close the original task in Linear

How to install linear-task-to-issue

1claude-code-templates

npx claude-code-templates@latest --command sync/linear-task-to-issue

2Manually: put the files in place

.claude/commands/linear-task-to-issue.md

Call it with /linear-task-to-issue. For all projects use ~/.claude/commands/

Manually: put the files in place

~/.codex/prompts/linear-task-to-issue.md

Call it with /prompts:linear-task-to-issue. Codex marks this format deprecated in favour of skills

Manually: put the files in place

.github/prompts/linear-task-to-issue.prompt.md

Manually: put the files in place

.gemini/commands/linear-task-to-issue.toml

Gemini stores commands as TOML: the prompt text goes into the prompt field

Questions about linear-task-to-issue

How do I install linear-task-to-issue in Claude Code?

Run npx claude-code-templates@latest --command sync/linear-task-to-issue. The command file lands at .claude/commands/linear-task-to-issue.md.

What does linear-task-to-issue do?

It creates a GitHub issue from a Linear task, copying fields, labels, assignees, milestone, attachments, comments and task relationships.

What does the command need to run?

An authenticated gh CLI and access to the Linear task. Use --skip-attachments to leave out the attachment step when the files are not reachable.

Source text

linear-task-to-issue.md · MIT

---
allowed-tools: Read, Write, Edit, Bash
argument-hint: "[task-id] | --repo | --milestone | --close-linear | --skip-attachments"
description: Convert Linear tasks to GitHub issues with relationship preservation and metadata mapping
---

# Linear Task to Issue

Convert Linear tasks to GitHub issues with comprehensive relationship mapping: **$ARGUMENTS**

## Current Task Context

- Task details: Based on $ARGUMENTS task identifier or selection criteria
- Target repository: !`gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No repo context"`
- User mappings: Linear email to GitHub username correspondence
- Attachment handling: Linear attachment access and GitHub upload capabilities

## Task

Execute precise conversion of Linear tasks to GitHub issues:

**Task Target**: Use $ARGUMENTS to specify task identifier, target repository, milestone mapping, or processing preferences

**Conversion Framework**:
1. **Task Analysis** - Fetch complete Linear task data, extract relationships, analyze content structure, identify priorities
2. **Content Transformation** - Build GitHub issue body, map Linear fields, preserve formatting, handle rich content
3. **GitHub Integration** - Create issue with proper structure, apply labels, assign users, set milestones, manage relationships
4. **Attachment Migration** - Download Linear attachments, upload to GitHub, update references, maintain accessibility
5. **Comment Import** - Transfer comments with attribution, preserve timestamps, maintain context, handle mentions
6. **Cross-Reference Setup** - Create bidirectional links, update Linear task, maintain sync database, enable navigation

**Advanced Features**: Rich content conversion, attachment handling, relationship mapping, user mention translation, comprehensive validation.

**Relationship Management**: Preserve parent-child relationships, maintain team context, map project associations, handle dependencies.

**Output**: Successfully created GitHub issue with complete data migration, accurate field mappings, preserved relationships, and comprehensive conversion report.

Similar slash commands

All slash commands for Notes, tasks and projects →

Linear Automation Claude Office Skills Automates Linear issue tracking, Git branch and PR syncing, and two-week cycle planning through project-mcp tools. CX Codex +1 4,600installs pr-link-issue getsentry Adds a GitHub issue and its linked Linear ticket to the current PR description. Use it when a pull request needs references to the work it addresses. CX Codex +1 1,200installs groove-utilities-task-analyse andreadellacorte Pulls tasks from your project backend and groups them by status, so you have something to write into daily memory. CX Codex +1 588installs groove-utilities-task-list andreadellacorte Pulls active tasks from your configured backend and shows what is in progress, ready or blocked. Handy as a daily starting view. CX Codex +1 577installs gh-issue-sync mitsuhiko Syncs GitHub Issues into local Markdown files for triage, search, editing, and issue creation from an editor or terminal. CX Codex +1 23,300installs linear-cli schpet This skill wires the linear CLI into your agent so it can search, create and update Linear issues from the terminal. CX Codex +1 14,100installs

From the same set361

The whole set →

publisher-medium Turns a blog post from markdown, PDF or a URL into HTML you can paste into Medium, with markers showing where images go. 134installs paper-2-web Turns an academic paper in LaTeX or PDF into an interactive homepage, a conference poster and a presentation video. Handy before a talk or when promoting a preprint. 133installs task-from-pr Turns a GitHub pull request into a Linear task, with a size estimate, team assignment and links running both ways. 133installs performance-profiling A Claude skill that keeps the agent on a fixed loop: measure, find the bottleneck, change one thing, confirm the result. Useful when a page drags. 132installs bulk-import-issues A slash command that migrates GitHub issues into Linear in batches, with filtering by label or milestone and retries when a batch fails. 129installs react-useeffect A skill that walks through React's useEffect rules from the official docs and points out what to use instead when an Effect is unnecessary. 127installs svelte-scaffold Builds out a new SvelteKit project, feature module or component library with a ready folder layout and config files. Handy when you want a starting point without wiring it by hand. 127installs vercel-deployment A Claude skill that tells your agent how to deploy Next.js to Vercel: env vars per environment, edge vs serverless, build cache. 124installs