mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
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>
1.6 KiB
1.6 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [migration-name] | --create-table | --add-column | --alter-table
description: Create and manage database migrations with proper versioning and rollback support
Create Database Migrations
Create and manage database migrations: $ARGUMENTS
Current Database State
- ORM detection: @package.json or @requirements.txt (detect Sequelize, Prisma, Alembic, etc.)
- Migration files: !
find . -name "*migration*" -type f | head -5 - Database config: @config/database.* or @prisma/schema.prisma
- Current schema: !
ls migrations/ 2>/dev/null | wc -lmigrations found
Task
Create comprehensive database migrations with proper versioning and rollback capabilities:
Migration Types: Use $ARGUMENTS to specify table creation, column addition, table alteration, or data migration
Migration Framework:
- Migration Planning - Analyze schema changes, dependencies, and data impact
- Migration Generation - Create timestamped migration files with up/down methods
- Schema Updates - Table creation, column modifications, index management
- Data Migrations - Safe data transformations and backfills
- Rollback Strategy - Implement reliable rollback procedures for each change
- Testing - Validate migrations in development and staging environments
Best Practices: Follow database-specific conventions, maintain referential integrity, handle large datasets efficiently, and ensure zero-downtime deployments.
Output: Production-ready migration files with comprehensive rollback support, proper indexing, and data safety measures.