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
Migration Assistant
Execute comprehensive system migrations with planning, verification, and rollback capabilities: $ARGUMENTS
Current Migration Context
- Source systems: GitHub CLI authentication and API access status
- Target systems: Linear MCP server connectivity and permissions
- Backup storage: Available storage space and backup verification
- Migration scope: Data volume estimation and complexity assessment
Task
Execute systematic migration process with comprehensive safety measures and validation:
Migration Action: Use $ARGUMENTS to specify migration planning, analysis, execution, verification, or rollback operations
Migration Framework:
- Prerequisites Validation - Verify GitHub CLI authentication, confirm Linear MCP connectivity, validate permissions, ensure backup storage
- Migration Planning - Assess data volume and complexity, design migration strategy, identify dependencies, create rollback plan
- Risk Analysis - Evaluate potential failure points, assess data integrity risks, identify system dependencies, plan contingency measures
- Execution Management - Implement migration phases, monitor progress and health, handle errors gracefully, maintain audit trails
- Verification Process - Validate data integrity, confirm system functionality, test user workflows, verify performance metrics
- Rollback Procedures - Implement safe rollback mechanisms, restore system state, validate recovery, communicate status updates
Advanced Features: Incremental migration support, real-time progress monitoring, automated health checks, comprehensive logging, emergency stop mechanisms.
Safety Measures: Multi-point backups, integrity validation, rollback testing, system health monitoring, stakeholder communication.
Output: Complete migration execution with progress tracking, validation reports, rollback readiness, and post-migration optimization recommendations.