Dani
054c0e56e9
Removed the deprecated 'model: sonnet' field from command frontmatter to fix compatibility issues with Claude Code. Commands will now inherit the model from the active conversation instead of using a hardcoded deprecated model identifier. Changes: - Removed 'model: sonnet' from 142 command files across all categories - Commands now use default model inheritance behavior - Preserved 'model: claude-sonnet-4-5-20250929' in gemini-review.md (valid model) - 67 commands without model field remain unchanged This resolves the "model: sonnet not found" error reported in GitHub issues and aligns with Claude Code's recommended practice of letting commands inherit the conversation model. Affected categories: - Database/Supabase commands (8 files) - Documentation commands (8 files) - Deployment commands (11 files) - Setup commands (14 files) - Performance commands (8 files) - Team commands (14 files) - Security commands (6 files) - NextJS/Vercel commands (10 files) - Sync commands (14 files) - And more across other categories 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.1 KiB
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.