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.8 KiB
1.8 KiB
allowed-tools: Read, Write, Edit, Bash
argument-hint: [platform] | --github-actions | --gitlab-ci | --azure-pipelines | --jenkins
description: Setup comprehensive CI/CD pipeline with automated testing, deployment, and monitoring
Setup CI/CD Pipeline
Setup comprehensive CI/CD pipeline with automated workflows and deployments: $ARGUMENTS
Current Repository State
- Version control: !
git remote -v | head -1(GitHub, GitLab, etc.) - Existing CI: !
find . -name ".github" -o -name ".gitlab-ci.yml" -o -name "azure-pipelines.yml" | wc -l - Test framework: @package.json or testing files detection
- Deployment config: @Dockerfile or deployment manifests
Task
Implement production-ready CI/CD pipeline with comprehensive automation and best practices:
Platform Choice: Use $ARGUMENTS to specify GitHub Actions, GitLab CI, Azure Pipelines, or Jenkins
Pipeline Architecture:
- Build Automation - Code compilation, dependency installation, artifact creation
- Testing Strategy - Unit tests, integration tests, e2e tests, code coverage reporting
- Quality Gates - Linting, security scanning, vulnerability assessment, code quality metrics
- Deployment Automation - Staging deployment, production deployment, rollback mechanisms
- Environment Management - Infrastructure provisioning, configuration management, secrets handling
- Monitoring Integration - Performance monitoring, error tracking, deployment notifications
Advanced Features: Parallel job execution, matrix builds, deployment strategies (blue-green, canary), and multi-environment support.
Security & Compliance: Secure credential management, compliance checks, audit trails, and approval workflows.
Output: Complete CI/CD pipeline with automated testing, secure deployments, monitoring integration, and comprehensive documentation.