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.5 KiB
1.5 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [version-type] | --patch | --minor | --major | --prerelease
description: Prepare and execute project release with version management and changelog updates
Project Release
Update CHANGELOG.md with changes since the last version increase. Check our README.md for any necessary changes. Check the scope of changes since the last release and increase our version number as appropriate: $ARGUMENTS
Current Project State
- Git status: !
git status --porcelain - Current version: !
git describe --tags --abbrev=0 2>/dev/null || echo "No previous tags" - Recent commits: !
git log --oneline --since="1 month ago" | head -10 - Package info: @package.json or @setup.py or @Cargo.toml (if exists)
Task
Prepare a project release following these steps:
- Analyze Changes: Review git history since last release to determine appropriate version increment
- Update Version: Update version in package.json, setup.py, or other version files based on semantic versioning
- Update Changelog: Add new entries to CHANGELOG.md with proper categorization (Added, Changed, Fixed, etc.)
- Update Documentation: Review and update README.md if necessary for new features or changes
- Create Release: Tag the release and prepare release notes
If version type is specified in $ARGUMENTS, use that increment. Otherwise, analyze the changes and suggest appropriate versioning.
Focus on maintaining proper semantic versioning and clear changelog documentation.