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>
36 lines
2.1 KiB
Markdown
36 lines
2.1 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [action] | --pull | --push | --diff | --validate
|
|
description: Synchronize database schema with Supabase using MCP integration
|
|
---
|
|
|
|
# Supabase Schema Sync
|
|
|
|
Synchronize database schema between local and Supabase with comprehensive validation: **$ARGUMENTS**
|
|
|
|
## Current Supabase Context
|
|
|
|
- MCP connection: Supabase MCP server with read-only access configured
|
|
- Local schema: !`find . -name "schema.sql" -o -name "migrations" -type d | head -3` local database files
|
|
- Project config: !`find . -name "supabase" -type d -o -name ".env*" | grep -v node_modules | head -3` configuration files
|
|
- Git status: !`git status --porcelain | grep -E "\\.sql$|\\.ts$" | head -5` database-related changes
|
|
|
|
## Task
|
|
|
|
Execute comprehensive schema synchronization with Supabase integration:
|
|
|
|
**Sync Action**: Use $ARGUMENTS to specify pull from remote, push to remote, diff comparison, or schema validation
|
|
|
|
**Schema Synchronization Framework**:
|
|
1. **MCP Integration** - Connect to Supabase via MCP server, authenticate with project credentials, validate connection status
|
|
2. **Schema Analysis** - Compare local vs remote schema, identify structural differences, analyze migration requirements, assess breaking changes
|
|
3. **Sync Operations** - Execute pull/push operations, apply schema migrations, handle conflict resolution, validate data integrity
|
|
4. **Validation Process** - Verify schema consistency, validate foreign key constraints, check index performance, test query compatibility
|
|
5. **Migration Management** - Generate migration scripts, track version history, implement rollback procedures, optimize execution order
|
|
6. **Safety Checks** - Backup critical data, validate permissions, check production impact, implement dry-run mode
|
|
|
|
**Advanced Features**: Automated conflict resolution, schema version control, performance impact analysis, team collaboration workflows, CI/CD integration.
|
|
|
|
**Quality Assurance**: Schema validation, data integrity checks, performance optimization, rollback readiness, team synchronization.
|
|
|
|
**Output**: Complete schema sync with validation reports, migration scripts, conflict resolution, and team collaboration updates. |