- sync-migration-assistant.md 36 lines · 2.1 KB
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:
- Pre-Migration Assessment - Data volume analysis, dependency mapping, risk assessment, resource planning
- Migration Planning - Phased approach design, rollback strategy, validation checkpoints, timeline estimation
- Data Extraction - Comprehensive data harvesting, relationship preservation, metadata capture, error handling
- Transformation Engine - Field mapping, format conversion, validation rules, data enrichment
- Migration Execution - Batch processing, progress tracking, error recovery, quality assurance
- 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.
Scanned by NVIDIA SkillSpector
Automated static analysis (no LLM) · v2.12.0 · 2026-10-23
SkillSpector looks for patterns such as shell commands, credential access, network calls or unpinned dependencies. An observation is something worth reading in the files before you install, not a confirmed vulnerability. Components that run code locally, like hooks, MCP servers and security tooling, naturally show more of them.
No observations.
Learn more about NVIDIA SkillSpector or how components are reviewed.