sync-issues-to-linear — Claude Code command: sync and install
Move GitHub issues into Linear with field and assignee mapping. Filter the set by state, labels, milestone, assignee, or specific issues.
npx claude-code-templates@latest --command sync/sync-issues-to-linearWhat sync-issues-to-linear does
The command reads issues from the current GitHub repository and creates corresponding tasks in a Linear workspace. You can narrow the selection by state, labels, assignee, milestone, or a specific set of issues. It maps GitHub fields to Linear, checks required data, and guards against duplicates.
It reads repository context and GitHub API rate-limit information. Operations are batched, with exponential backoff for rate limits; progress, errors, and sync results are reported. The command can also assign teams and projects, maintain task relationships, and perform incremental syncs. Tasks are created in Linear, so check the target workspace and filters before running it.
What it helps with
- move GitHub issues into Linear
- filter a sync by issue state or labels
- map issue assignees and priorities
- check for duplicate tasks during transfer
Example prompts for the agent
- Sync all issues from the current repository to Linear.
- Transfer open issues labeled
bugto Linear. - Sync issues assigned to
aliceand report the results.
How to install sync-issues-to-linear
1claude-code-templates
npx claude-code-templates@latest --command sync/sync-issues-to-linear2Manually: put the files in place
.claude/commands/sync-issues-to-linear.mdCall it with /sync-issues-to-linear. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/sync-issues-to-linear.mdCall it with /prompts:sync-issues-to-linear. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/sync-issues-to-linear.prompt.mdManually: put the files in place
.gemini/commands/sync-issues-to-linear.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about sync-issues-to-linear
How do I install sync-issues-to-linear in Claude Code?
Run npx claude-code-templates@latest --command sync/sync-issues-to-linear, then place the command file at .claude/commands/sync-issues-to-linear.md.
What does sync-issues-to-linear do?
It transfers GitHub issues to Linear, maps fields and assignments, checks for duplicates, and reports sync results.
Which issues can I sync?
Filter the selection by state, labels, assignee, milestone, or specific issues.
Source text
sync-issues-to-linear.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[sync-scope] | --state | --label | --assignee | --milestone" description: Sync GitHub issues to Linear workspace with comprehensive field mapping and rate limit management --- # Sync Issues to Linear Sync GitHub issues to Linear workspace with intelligent field mapping: **$ARGUMENTS** ## Current Repository Context - Repository: !`gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No repo context"` - Issue count: !`gh issue list --state all --limit 1 --json number | jq length 2>/dev/null || echo "Check manually"` - Linear teams: Available Linear teams and project assignments - Rate limits: !`gh api rate_limit -q '.rate | "GitHub: \(.remaining)/\(.limit)"' 2>/dev/null` ## Task Execute comprehensive synchronization of GitHub issues to Linear workspace: **Sync Scope**: Use $ARGUMENTS to filter by issue state, labels, assignees, milestones, or specific issue sets **Synchronization Framework**: 1. **Issue Discovery** - Fetch GitHub issues with comprehensive metadata, apply filters, validate requirements 2. **Field Mapping** - Transform GitHub fields to Linear format, map priorities, convert labels, handle assignees 3. **Data Validation** - Check required fields, validate user mappings, ensure data integrity, prevent duplicates 4. **Linear Integration** - Create tasks with proper formatting, apply team assignments, set projects, manage relationships 5. **Rate Limit Management** - Implement exponential backoff, batch operations, monitor API limits, optimize requests 6. **Progress Tracking** - Provide real-time updates, handle errors gracefully, maintain sync state, generate reports **Advanced Features**: Smart priority inference, intelligent user mapping, incremental sync capabilities, comprehensive error recovery. **Data Integrity**: Preserve formatting, maintain metadata, create bidirectional references, ensure audit trails. **Output**: Complete synchronization results with success metrics, error reports, mapping summaries, and comprehensive sync analytics.
© davila7 · MIT · davila7/claude-code-templates