Power Issue To Linear

Convert individual GitHub issues to Linear tasks with comprehensive field mapping, metadata preservation, and bidirectional reference linking.

When to Use This Command

Run this command when...

• You need to convert a specific GitHub issue to a Linear task with precise control over field mapping, team assignment, and project placement
• You want to preserve all metadata including labels, assignees, comments, and linked pull requests during the conversion
• Your workflow requires creating Linear tasks from GitHub issues on-demand with automatic cross-referencing between platforms

Do NOT use this command when...

• You need to migrate many issues at once -- use the bulk import command for batch operations
• You want ongoing synchronization -- use the bidirectional invoker for continuous sync

Quick Start

Copy
# .claude/commands/power-issue-to-linear.md
# Convert GitHub issue to Linear task
Convert: $ARGUMENTS

Copy
# Run the command
claude "power-issue-to-linear convert issue #142 to Linear task in Backend team with High priority"

Expected output:
- Linear task created with mapped title and description
- Labels converted from GitHub to Linear equivalents
- Assignee mapped to Linear team member
- Comments transferred as Linear task comments
- Cross-reference links added to both platforms

Core Concepts

Concept	Description
Field Mapping	Converting GitHub issue fields to their Linear task equivalents
Metadata Preservation	Carrying over labels, assignees, milestones, and comments
Priority Mapping	Translating GitHub priority labels to Linear priority levels
Cross-Referencing	Adding bidirectional links between the GitHub issue and Linear task
Comment Transfer	Copying issue discussion threads to the new Linear task

Conversion Pipeline:

  GitHub Issue #N
       |
  [Fetch Issue Data]
  |    |    |    |
 Title Body Labels Comments
  |    |    |    |
  [Map Fields to Linear]
       |
  [Create Linear Task]
       |
  [Transfer Comments]
       |
  [Add Cross-References]
       |
  Linear Task + Linked GitHub Issue

Configuration

Parameter	Default	Description
Linear Team	Required	Target Linear team for the created task
Priority	Auto-map from labels	Linear priority level (Urgent, High, Medium, Low, None)
Project	None	Optional Linear project assignment
Comment Transfer	All comments	Whether to transfer none, recent, or all comments
Cross-Reference	Both platforms	Add links on GitHub issue and Linear task

Best Practices

1. Specify the target team -- Linear requires a team assignment. Always include which team should own the converted task in your arguments
2. Map priority labels explicitly -- if your GitHub issues use labels like "P0" or "critical", mention how they should map to Linear's priority levels
3. Include project context -- assigning the Linear task to a project and cycle during creation saves manual organization work later
4. Transfer comments selectively -- for issues with long discussion threads, consider transferring only the most recent or most relevant comments
5. Verify cross-references -- after conversion, check that both the GitHub issue and Linear task contain working links to each other

Common Issues

1. Assignee not found in Linear -- GitHub usernames do not automatically match Linear accounts. Specify the Linear user or provide a username mapping
2. Labels do not exist in Linear -- GitHub labels must exist in the target Linear team before they can be applied. Create them first or specify label mappings
3. Markdown formatting differences -- GitHub and Linear use slightly different Markdown extensions. Complex formatting like task lists or mermaid diagrams may need manual adjustment