mirror of
https://github.com/davila7/claude-code-templates.git
synced 2026-09-19 01:30:23 +08:00
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>
2.2 KiB
2.2 KiB
allowed-tools: Read, Write, Edit, Glob
argument-hint: [scope] | --claude-md | --documentation | --outdated-patterns | --implementation-sync
description: Clean and organize project memory files with implementation synchronization and pattern updates
Memory Spring Cleaning
Clean and synchronize project memory with current implementation patterns: $ARGUMENTS
Current Memory Context
- Memory files: !
find . -name "CLAUDE*.md" | wc -lCLAUDE.md files in project - Documentation: !
find . -name "README*" -o -name "*.md" | wc -ltotal documentation files - Last update: !
find . -name "CLAUDE.md" -exec stat -c "%y" {} \; 2>/dev/null | head -1 || echo "No CLAUDE.md found" - Implementation drift: Analysis of documented vs actual patterns
Task
Execute comprehensive memory cleanup with implementation synchronization:
Cleanup Scope: Use $ARGUMENTS to focus on CLAUDE.md files, general documentation, outdated pattern identification, or implementation synchronization
Memory Cleaning Framework:
- Memory File Discovery - Locate all CLAUDE.md and documentation files, assess hierarchy and organization, identify redundant content
- Implementation Analysis - Compare documented patterns with actual code, identify implementation drift, assess accuracy gaps
- Pattern Validation - Verify documented conventions, validate code examples, check dependency accuracy, assess technology stack alignment
- Content Optimization - Remove outdated information, consolidate duplicate content, improve organization structure, enhance clarity
- Synchronization Updates - Update development commands, refresh technology stack references, sync architectural patterns, validate workflows
- Quality Assurance - Ensure consistency across files, validate markdown formatting, check link integrity, maintain version alignment
Advanced Features: Automated pattern detection, implementation drift analysis, cross-reference validation, documentation health scoring.
Memory Health: Content freshness metrics, accuracy validation, usage pattern analysis, maintenance scheduling recommendations.
Output: Cleaned and synchronized memory files with updated patterns, validated implementations, and maintenance recommendations.