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.9 KiB
1.9 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [update-strategy] | --patch | --minor | --major | --security-only
description: Update and modernize project dependencies with comprehensive testing and compatibility checks
Update Dependencies
Update and modernize project dependencies with safety checks: $ARGUMENTS
Current Dependencies State
- Package manager: @package.json or @requirements.txt or @Cargo.toml (detect package manager)
- Outdated packages: !
npm outdated 2>/dev/null || pip list --outdated 2>/dev/null || echo "Manual check needed" - Security issues: !
npm audit --audit-level=moderate 2>/dev/null || pip check 2>/dev/null || echo "Run security audit" - Lock files: @package-lock.json or @poetry.lock or @Cargo.lock
Task
Systematically update project dependencies with comprehensive testing and compatibility validation:
Update Strategy: Use $ARGUMENTS to specify patch updates, minor updates, major updates, or security-only updates
Update Process:
- Dependency Analysis - Audit current versions, identify outdated packages, assess security vulnerabilities
- Impact Assessment - Check changelogs, breaking changes, deprecation warnings, compatibility matrix
- Staged Updates - Apply patch updates first, then minor, finally major versions with testing between stages
- Testing & Validation - Run full test suite, build verification, integration testing, performance checks
- Rollback Strategy - Document changes, create restore points, maintain rollback procedures
- Documentation Updates - Update README, dependencies list, migration guides, team notifications
Safety Features: Automated testing between updates, dependency conflict resolution, security vulnerability prioritization.
Output: Updated dependency manifest with comprehensive testing results, security audit report, and upgrade documentation.