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, Bash
argument-hint: [scope] | --file | --epic | --fix | --pre-commit
description: Validate Product as Code project structure and files for PAC specification compliance
Validate PAC Structure
Validate Product as Code project structure and files for PAC specification compliance: $ARGUMENTS
Current PAC State
- PAC directory: !
ls -la .pac/ 2>/dev/null || echo "No .pac directory found" - Configuration: @.pac/pac.config.yaml (if exists)
- Epic count: !
find .pac/epics/ -name "*.yaml" 2>/dev/null | wc -l - Ticket count: !
find .pac/tickets/ -name "*.yaml" 2>/dev/null | wc -l
Task
Comprehensive validation of PAC project structure and specification compliance:
Validation Scope: Use $ARGUMENTS for specific files/epics or validate entire PAC structure
Validation Checks:
- Structure Validation - Directory structure and required files
- Configuration Compliance - PAC config file format and values
- Epic Validation - YAML syntax, required fields, and spec compliance
- Ticket Validation - Format, metadata, and epic references
- Cross-Reference Integrity - Epic-ticket relationships and dependencies
- Data Consistency - Timestamps, status transitions, and ID uniqueness
Output: Detailed validation report with compliance status, issues found, and specific recommendations for fixes. Use --fix to automatically resolve common issues.
Exit Codes: 0 (valid), 1 (errors found), 2 (configuration issues)