sync-migration-assistant — Claude Code command: move GitHub
A slash command that migrates issues between GitHub and Linear with validation and rollback. Useful when a project changes trackers.
npx claude-code-templates@latest --command sync/sync-migration-assistantWhat sync-migration-assistant does
The command moves data between GitHub and Linear. You pick the direction with an argument: --github-to-linear, --linear-to-github, --bidirectional or --validate. Work runs in stages — volume assessment, planning with rollback checkpoints, extraction, field transformation, batch writing, then an integrity check on the other side.
The toolset is plain: Read, Write, Edit and Bash. At startup it checks the environment, running gh --version for the GitHub CLI and looking at Linear MCP server connectivity. No GitHub CLI means the first step fails right away, so install it before you run anything. Linear needs an authenticated MCP server.
Rollback is the point. Tracker migrations break on issue relationships and field mismatches, so the command builds a phased plan with checkpoints instead of writing straight away. On a large dataset, run --validate first — that is the cheap way to find mapping gaps.
What it helps with
- move issues from GitHub to Linear
- verify data integrity after a migration
- plan a tracker move with rollback checkpoints
- set up two-way sync between trackers
- check issue relationships before transferring
Example prompts for the agent
- /sync-migration-assistant --github-to-linear
- /sync-migration-assistant --validate
- /sync-migration-assistant --bidirectional
How to install sync-migration-assistant
1claude-code-templates
npx claude-code-templates@latest --command sync/sync-migration-assistant2Manually: put the files in place
.claude/commands/sync-migration-assistant.mdCall it with /sync-migration-assistant. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/sync-migration-assistant.mdCall it with /prompts:sync-migration-assistant. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/sync-migration-assistant.prompt.mdManually: put the files in place
.gemini/commands/sync-migration-assistant.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about sync-migration-assistant
How do I install sync-migration-assistant in Claude?
Run npx claude-code-templates@latest --command sync/sync-migration-assistant, then confirm the file landed at .claude/commands/sync-migration-assistant.md.
What does sync-migration-assistant do?
It migrates data between GitHub and Linear in phases: assessment, planning, extraction, transformation, execution and post-migration validation. Rollback and a validation-only mode are included.
What does the command need to run?
The GitHub CLI for GitHub access and an authenticated Linear MCP server. The command checks both at startup.
Source text
sync-migration-assistant.md · MIT
--- allowed-tools: Read, Write, Edit, Bash argument-hint: "[migration-type] | --github-to-linear | --linear-to-github | --bidirectional | --validate" description: Comprehensive migration assistant for large-scale GitHub-Linear data transitions with validation and rollback --- # Sync Migration Assistant Execute comprehensive data migration between GitHub and Linear with enterprise-grade capabilities: **$ARGUMENTS** ## Current Migration Environment - Source system: !`gh --version 2>/dev/null && echo "GitHub CLI available" || echo "GitHub CLI needed"` - Target system: Linear MCP server connectivity and authentication status - Migration scope: Analysis of data volume and complexity for planning - Infrastructure: Database, queue services, and processing capacity assessment ## Task Implement large-scale data migration with comprehensive validation and enterprise features: **Migration Type**: Use $ARGUMENTS to specify GitHub-to-Linear, Linear-to-GitHub, bidirectional setup, or validation mode **Migration Framework**: 1. **Pre-Migration Assessment** - Data volume analysis, dependency mapping, risk assessment, resource planning 2. **Migration Planning** - Phased approach design, rollback strategy, validation checkpoints, timeline estimation 3. **Data Extraction** - Comprehensive data harvesting, relationship preservation, metadata capture, error handling 4. **Transformation Engine** - Field mapping, format conversion, validation rules, data enrichment 5. **Migration Execution** - Batch processing, progress tracking, error recovery, quality assurance 6. **Post-Migration Validation** - Data integrity verification, relationship validation, performance testing, rollback readiness **Enterprise Features**: Large-scale batch processing, comprehensive error recovery, detailed audit trails, rollback capabilities, performance optimization. **Quality Assurance**: Multi-stage validation, data integrity checks, relationship verification, comprehensive testing, enterprise monitoring. **Output**: Complete migration system with phased execution, comprehensive validation, detailed reporting, and enterprise-grade reliability for large-scale data transitions.
© davila7 · MIT · davila7/claude-code-templates