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.3 KiB
Markdown
36 lines
2.3 KiB
Markdown
---
|
|
allowed-tools: Read, Write, Edit, Bash
|
|
argument-hint: [operation] | --backup | --restore | --schedule | --validate | --cleanup
|
|
description: Manage Supabase database backups with automated scheduling and recovery procedures
|
|
---
|
|
|
|
# Supabase Backup Manager
|
|
|
|
Manage comprehensive Supabase database backups with automated scheduling and recovery validation: **$ARGUMENTS**
|
|
|
|
## Current Backup Context
|
|
|
|
- Supabase project: MCP integration for backup operations and status monitoring
|
|
- Backup storage: Current backup configuration and storage capacity
|
|
- Recovery testing: Last backup validation and recovery procedure verification
|
|
- Automation status: !`find . -name "*.yml" -o -name "*.json" | xargs grep -l "backup\|cron" 2>/dev/null | head -3` scheduled backup configuration
|
|
|
|
## Task
|
|
|
|
Execute comprehensive backup management with automated procedures and recovery validation:
|
|
|
|
**Backup Operation**: Use $ARGUMENTS to specify backup creation, data restoration, schedule management, backup validation, or cleanup procedures
|
|
|
|
**Backup Management Framework**:
|
|
1. **Backup Strategy** - Design backup schedules, implement retention policies, configure incremental backups, optimize storage usage
|
|
2. **Automated Backup** - Create database snapshots, export schema and data, validate backup integrity, monitor backup completion
|
|
3. **Recovery Procedures** - Test restore processes, validate data integrity, implement point-in-time recovery, optimize recovery time
|
|
4. **Schedule Management** - Configure automated backup schedules, implement backup monitoring, setup failure notifications, optimize backup windows
|
|
5. **Storage Optimization** - Manage backup storage, implement compression strategies, archive old backups, monitor storage costs
|
|
6. **Disaster Recovery** - Plan disaster recovery procedures, test recovery scenarios, document recovery processes, validate business continuity
|
|
|
|
**Advanced Features**: Automated backup validation, recovery time optimization, cross-region backup replication, backup encryption, compliance reporting.
|
|
|
|
**Monitoring Integration**: Backup success monitoring, failure alerting, storage usage tracking, recovery time measurement, compliance reporting.
|
|
|
|
**Output**: Complete backup management system with automated schedules, recovery procedures, validation reports, and disaster recovery planning. |