Skip to main content
command CX Codex

sync-linear-to-issues · qdhenry — Claude Code command: setup guide

sync-linear-to-issues exports Linear tasks into GitHub issues while preserving issue descriptions, sprint milestones, and status mappings.

no license ★ 1,357 updated 2026-03-01

Install into Claude Code · Manually: put the files in place All methods and platforms ↓
.claude/commands/sync-linear-to-issues.md
Open on GitHub

What sync-linear-to-issues does

This command retrieves issues from Linear via MCP and writes them to GitHub using the gh CLI tool. It maps task titles, acceptance criteria, assignees, and projects directly to GitHub issue fields and milestones. Active states like Backlog, Todo, or In Review map to open issues, while Done or Canceled states map to closed issues.

Issue priorities turn into labels such as priority/high or priority/urgent. Each created issue gets a footer containing the Linear identifier and a direct URL. It also copies attachments, syncs comments, and handles API rate limits by sending requests in batches of 20 with a two-second delay.

The routine fails immediately if your gh CLI is unauthenticated or the Linear MCP server is absent.

What it helps with

  • Export active Linear tasks into a GitHub repository
  • Convert Linear priority levels into standardized GitHub labels
  • Backfill comments and attachment links into GitHub issues
  • Track Linear ticket identifiers directly in issue footers

Example prompts for the agent

  • Sync all tasks from Linear team ENG to this GitHub repository
  • Import Linear tasks for project Sprint 23 with urgent and high priority
  • Update existing GitHub issues with fresh comments from Linear

How to install sync-linear-to-issues

Manually: put the files in place

.claude/commands/sync-linear-to-issues.md

Call it with /sync-linear-to-issues. For all projects use ~/.claude/commands/

Questions about sync-linear-to-issues

How to install sync-linear-to-issues in Claude Code?

Save the command definition file directly to .claude/commands/sync-linear-to-issues.md in your project directory.

What does sync-linear-to-issues do?

It reads tasks from Linear via an MCP server and creates matching GitHub issues with converted statuses, labels, and metadata.

What dependencies are required to run this command?

You need an active Linear MCP server connection and an authenticated gh command-line tool targeted at your repository.

Similar slash commands

All slash commands for Notes, tasks and projects →

sync-linear-to-issues by other authors comes first.

sync-linear-to-issues davila7 sync-linear-to-issues transfers Linear tasks to GitHub issues with state mapping, attachment migration, and comment sync. Useful when consolidating project tracking into GitHub. CX Codex +1 123installs sync-issues-to-linear davila7 sync-issues-to-linear is a Claude Code command that transfers GitHub issues to Linear, mapping fields and assignees; filters select which tasks to sync. CX Codex +1 128installs bidirectional-sync davila7 bidirectional-sync sets up two-way synchronization between GitHub Issues and Linear tasks. Handles update conflicts and tracks state in local JSON files. CX Codex +1 133installs Linear Automation Claude Office Skills Linear Automation automates Linear issue tracking, Git branch and PR syncing, and two-week cycle planning through project-mcp tools. CX Codex +1 4,800installs bulk-import-issues BuildWithClaude Community bulk-import-issues moves GitHub issues into Linear in batches, with duplicate checks, progress reporting, retries, and API limit handling. CX Codex +1 ★ 3,785repo stars groove-utilities-task-list andreadellacorte groove-utilities-task-list — a skill for Claude Code and five other platforms that pulls active tasks from a configured backend and groups them by status. In-progress work surfaces first, blocked tasks show what they are waiting on. CX Codex +1 579installs implement-task-linear PinguApps implement-task-linear — a skill for Claude Code bundles multiple Linear issues into a single branch and pull request. It coordinates ticket states, incremental commits, and pre-PR reviews before merging. CX Codex +1 346installs

From the same set112

The whole set →
prepare-release The prepare-release command walks through release preparation, from checks and version updates to build validation and Git tagging. Use it when a release needs a defined checklist. CX Codex +1 ★ 1,357repo stars hotfix-deploy hotfix-deploy is a Claude Code command that guides critical fixes through incident triage, testing, release monitoring, and rollback. CX Codex +1 ★ 1,357repo stars sync-status The sync-status command for Claude Code checks GitHub–Linear sync health, queues, webhooks, failures, and data mismatches. It supports diagnosis of synchronization issues. CX Codex +1 ★ 1,357repo stars performance-auditor performance-auditor — a subagent that hunts bottlenecks: algorithm cost, N+1 queries, bundle size, wasted re-renders. You get a prioritized report. CX Codex ★ 1,357repo stars task-from-pr task-from-pr is a Claude Code command that transfers GitHub pull request details to a Linear task, linking PR work with project tasks. CX Codex +1 ★ 1,357repo stars memory-merge The memory-merge command consolidates multiple semantic tree nodes into one, removing duplicates and grouping related concepts under a single node. CX Codex +1 ★ 1,357repo stars sync-conflict-resolver The sync-conflict-resolver command for Claude Code identifies and resolves data conflicts between GitHub issues and Linear tasks, merging non-conflicting fields or applying a chosen strategy. CX Codex +1 ★ 1,357repo stars standup-report standup-report builds daily standup updates from Git, GitHub, and Linear, with output suited to a team summary, Slack, or email. CX Codex +1 ★ 1,357repo stars

Project sponsors

Companies that keep this analytics open