Easy Linear Task To

Quickly convert GitHub issues to Linear tasks with sensible defaults, minimal configuration, and automatic field mapping for streamlined cross-platform task management.

When to Use This Command

Run this command when...

• You need to quickly move a GitHub issue to Linear without spending time on detailed field mapping configuration
• You want a fast, opinionated conversion that applies sensible defaults for priority, labels, and team assignment
• Your team regularly converts individual issues from GitHub to Linear as part of their daily workflow and needs minimal friction

Do NOT use this command when...

• You need fine-grained control over every field mapping -- use the power issue-to-linear command for detailed configuration
• You want to convert many issues at once -- use the bulk import command for batch operations

Quick Start

Copy
# .claude/commands/easy-linear-task-to.md
# Quick GitHub to Linear conversion
Convert: $ARGUMENTS

Copy
# Run the command
claude "easy-linear-task-to move issue #87 to Linear"

Expected output:
- Linear task created with auto-mapped fields
- Default priority based on GitHub labels
- Team assignment based on repository mapping
- Cross-reference link on both platforms
- Conversion confirmation with Linear task URL

Core Concepts

Concept	Description
Auto-Mapping	Automatic field conversion using naming conventions and label matching
Sensible Defaults	Pre-configured priority, status, and team mappings that work for most projects
Quick Reference	Automatic cross-reference link creation on both platforms
Minimal Input	Requires only the issue number -- all other fields are inferred from context
Convention Over Configuration	Uses standard patterns rather than requiring explicit mapping files

Quick Conversion Flow:

  GitHub Issue #N
       |
  [Auto-Detect Context]
  |         |
 Repo    Labels
  |         |
  [Apply Default Mappings]
       |
  [Create Linear Task]
       |
  [Add Quick References]
       |
  Done (Linear URL returned)

Configuration

Parameter	Default	Description
Team	Auto-detect from repo	Linear team inferred from repository name or mapping
Priority	Medium	Default priority unless GitHub labels indicate otherwise
Status	Backlog	Initial Linear task status
Comments	Skip	Comments are not transferred by default for speed
Cross-Reference	GitHub issue only	Adds Linear link to GitHub issue comment

Best Practices

1. Use for ad-hoc conversions -- this command is optimized for quick one-off conversions. For planned migrations, use bulk import instead
2. Set up repository-to-team mapping -- if you consistently convert issues from the same repositories, configure a default team mapping to eliminate the team specification step
3. Review after conversion -- the task is created with sensible defaults, but verify the priority and project assignment in Linear match your actual needs
4. Add context in arguments -- while the command works with just an issue number, adding "with high priority in Sprint 12" overrides defaults for better placement
5. Use for triage workflows -- this command works well in issue triage sessions where you quickly sort GitHub issues into Linear for team execution

Common Issues

1. Wrong team assigned -- auto-detection uses repository name matching which may not align with your Linear team structure. Specify the team explicitly if the default is wrong
2. Priority does not match expectations -- the default is Medium. If your GitHub labels encode priority differently, either specify the priority or set up a label-to-priority mapping
3. Missing context in Linear task -- since comments are skipped by default, important discussion context may be lost. Add "with comments" to your arguments for issues with relevant discussion threads