claude-code-templates 1.21.13 → 1.22.0

package/cli-tool/components/commands/deployment/hotfix-deploy.md

@@ -1,283 +0,0 @@
----
-allowed-tools: Read, Edit, Bash
-argument-hint: [hotfix-type] | --security | --critical | --rollback-ready | --emergency
-description: Deploy critical hotfixes with emergency procedures, validation, and rollback capabilities
-model: sonnet
----
-
-# Emergency Hotfix Deployment
-
-Deploy critical hotfix: $ARGUMENTS
-
-## Current Production State
-
-- Current version: !`git describe --tags --abbrev=0 2>/dev/null || echo "No tags found"`
-- Production branch: !`git branch --show-current`
-- Recent commits: !`git log --oneline -5`
-- Deployment status: !`curl -s https://api.example.com/health 2>/dev/null | jq -r '.version // "Unknown"' || echo "Health check failed"`
-- Staging environment: Check for staging deployment capabilities
-
-## Emergency Response Protocol
-
-Execute emergency hotfix deployment: $ARGUMENTS
-
-1. **Emergency Assessment and Triage**
-   - Assess the severity and impact of the issue
-   - Determine if a hotfix is necessary or if it can wait
-   - Identify affected systems and user impact
-   - Estimate time sensitivity and business impact
-   - Document the incident and decision rationale
-
-2. **Incident Response Setup**
-   - Create incident tracking in your incident management system
-   - Set up war room or communication channel
-   - Notify stakeholders and on-call team members
-   - Establish clear communication protocols
-   - Document initial incident details and timeline
-
-3. **Branch and Environment Setup**
-   ```bash
-   # Create hotfix branch from production tag
-   git fetch --tags
-   git checkout tags/v1.2.3  # Latest production version
-   git checkout -b hotfix/critical-auth-fix
-   
-   # Alternative: Branch from main if using trunk-based development
-   git checkout main
-   git pull origin main
-   git checkout -b hotfix/critical-auth-fix
-   ```
-
-4. **Rapid Development Process**
-   - Keep changes minimal and focused on the critical issue only
-   - Avoid refactoring, optimization, or unrelated improvements
-   - Use well-tested patterns and established approaches
-   - Add minimal logging for troubleshooting purposes
-   - Follow existing code conventions and patterns
-
-5. **Accelerated Testing**
-   ```bash
-   # Run focused tests related to the fix
-   npm test -- --testPathPattern=auth
-   npm run test:security
-   
-   # Manual testing checklist
-   # [ ] Core functionality works correctly
-   # [ ] Hotfix resolves the critical issue
-   # [ ] No new issues introduced
-   # [ ] Critical user flows remain functional
-   ```
-
-6. **Fast-Track Code Review**
-   - Get expedited review from senior team member
-   - Focus review on security and correctness
-   - Use pair programming if available and time permits
-   - Document review decisions and rationale quickly
-   - Ensure proper approval process even under time pressure
-
-7. **Version and Tagging**
-   ```bash
-   # Update version for hotfix
-   # 1.2.3 -> 1.2.4 (patch version)
-   # or 1.2.3 -> 1.2.3-hotfix.1 (hotfix identifier)
-   
-   # Commit with detailed message
-   git add .
-   git commit -m "hotfix: fix critical authentication vulnerability
-   
-   - Fix password validation logic
-   - Resolve security issue allowing bypass
-   - Minimal change to reduce deployment risk
-   
-   Fixes: #1234"
-   
-   # Tag the hotfix version
-   git tag -a v1.2.4 -m "Hotfix v1.2.4: Critical auth security fix"
-   git push origin hotfix/critical-auth-fix
-   git push origin v1.2.4
-   ```
-
-8. **Staging Deployment and Validation**
-   ```bash
-   # Deploy to staging environment for final validation
-   ./deploy-staging.sh v1.2.4
-   
-   # Critical path testing
-   curl -X POST staging.example.com/api/auth/login \
-        -H "Content-Type: application/json" \
-        -d '{"email":"test@example.com","password":"testpass"}'
-   
-   # Run smoke tests
-   npm run test:smoke:staging
-   ```
-
-9. **Production Deployment Strategy**
-   
-   **Blue-Green Deployment:**
-   ```bash
-   # Deploy to blue environment
-   ./deploy-blue.sh v1.2.4
-   
-   # Validate blue environment health
-   ./health-check-blue.sh
-   
-   # Switch traffic to blue environment
-   ./switch-to-blue.sh
-   
-   # Monitor deployment metrics
-   ./monitor-deployment.sh
-   ```
-   
-   **Rolling Deployment:**
-   ```bash
-   # Deploy to subset of servers first
-   ./deploy-rolling.sh v1.2.4 --batch-size 1
-   
-   # Monitor each batch deployment
-   ./monitor-batch.sh
-   
-   # Continue with next batch if healthy
-   ./deploy-next-batch.sh
-   ```
-
-10. **Pre-Deployment Checklist**
-    ```bash
-    # Verify all prerequisites are met
-    # [ ] Database backup completed successfully
-    # [ ] Rollback plan documented and ready
-    # [ ] Monitoring alerts configured and active
-    # [ ] Team members standing by for support
-    # [ ] Communication channels established
-    
-    # Execute production deployment
-    ./deploy-production.sh v1.2.4
-    
-    # Run immediate post-deployment validation
-    ./validate-hotfix.sh
-    ```
-
-11. **Real-Time Monitoring**
-    ```bash
-    # Monitor key application metrics
-    watch -n 10 'curl -s https://api.example.com/health | jq .'
-    
-    # Monitor error rates and logs
-    tail -f /var/log/app/error.log | grep -i "auth"
-    
-    # Track critical metrics:
-    # - Response times and latency
-    # - Error rates and exception counts
-    # - User authentication success rates
-    # - System resource usage (CPU, memory)
-    ```
-
-12. **Post-Deployment Validation**
-    ```bash
-    # Run comprehensive validation tests
-    ./test-critical-paths.sh
-    
-    # Test user authentication functionality
-    curl -X POST https://api.example.com/auth/login \
-         -H "Content-Type: application/json" \
-         -d '{"email":"test@example.com","password":"testpass"}'
-    
-    # Validate security fix effectiveness
-    ./security-validation.sh
-    
-    # Check overall system performance
-    ./performance-check.sh
-    ```
-
-13. **Communication and Status Updates**
-    - Provide regular status updates to stakeholders
-    - Use consistent communication channels
-    - Document deployment progress and results
-    - Update incident tracking systems
-    - Notify relevant teams of deployment completion
-
-14. **Rollback Procedures**
-    ```bash
-    # Automated rollback script
-    #!/bin/bash
-    PREVIOUS_VERSION="v1.2.3"
-    
-    if [ "$1" = "rollback" ]; then
-        echo "Rolling back to $PREVIOUS_VERSION"
-        ./deploy-production.sh $PREVIOUS_VERSION
-        ./validate-rollback.sh
-        echo "Rollback completed successfully"
-    fi
-    
-    # Manual rollback steps if automation fails:
-    # 1. Switch load balancer back to previous version
-    # 2. Validate previous version health and functionality
-    # 3. Monitor system stability after rollback
-    # 4. Communicate rollback status to team
-    ```
-
-15. **Post-Deployment Monitoring Period**
-    - Monitor system for 2-4 hours after deployment
-    - Watch error rates and performance metrics closely
-    - Check user feedback and support ticket volume
-    - Validate that the hotfix resolves the original issue
-    - Document any issues or unexpected behaviors
-
-16. **Documentation and Incident Reporting**
-    - Document the complete hotfix process and timeline
-    - Record lessons learned and process improvements
-    - Update incident management systems with resolution
-    - Create post-incident review materials
-    - Share knowledge with team for future reference
-
-17. **Merge Back to Main Branch**
-    ```bash
-    # After successful hotfix deployment and validation
-    git checkout main
-    git pull origin main
-    git merge hotfix/critical-auth-fix
-    git push origin main
-    
-    # Clean up hotfix branch
-    git branch -d hotfix/critical-auth-fix
-    git push origin --delete hotfix/critical-auth-fix
-    ```
-
-18. **Post-Incident Activities**
-    - Schedule and conduct post-incident review meeting
-    - Update runbooks and emergency procedures
-    - Identify and implement process improvements
-    - Update monitoring and alerting configurations
-    - Plan preventive measures to avoid similar issues
-
-**Hotfix Best Practices:**
-
-- **Keep It Simple:** Make minimal changes focused only on the critical issue
-- **Test Thoroughly:** Maintain testing standards even under time pressure
-- **Communicate Clearly:** Keep all stakeholders informed throughout the process
-- **Monitor Closely:** Watch the fix carefully in production environment
-- **Document Everything:** Record all decisions and actions for post-incident review
-- **Plan for Rollback:** Always have a tested way to revert changes quickly
-- **Learn and Improve:** Use each incident to strengthen processes and procedures
-
-**Emergency Escalation Guidelines:**
-
-```bash
-# Emergency contact information
-ON_CALL_ENGINEER="+1-555-0123"
-SENIOR_ENGINEER="+1-555-0124"
-ENGINEERING_MANAGER="+1-555-0125"
-INCIDENT_COMMANDER="+1-555-0126"
-
-# Escalation timeline thresholds:
-# 15 minutes: Escalate to senior engineer
-# 30 minutes: Escalate to engineering manager
-# 60 minutes: Escalate to incident commander
-```
-
-**Important Reminders:**
-
-- Hotfixes should only be used for genuine production emergencies
-- When in doubt about severity, follow the normal release process
-- Always prioritize system stability over speed of deployment
-- Maintain clear audit trails for all emergency changes
-- Regular drills help ensure team readiness for real emergencies

package/cli-tool/components/commands/deployment/prepare-release.md

@@ -1,357 +0,0 @@
----
-allowed-tools: Read, Write, Edit, Bash
-argument-hint: [version-type] | patch | minor | major | --pre-release | --hotfix
-description: Prepare and validate release packages with comprehensive testing, documentation, and automation
-model: sonnet
----
-
-# Release Preparation
-
-Prepare and validate release: $ARGUMENTS
-
-## Current Release Context
-
-- Current version: !`git describe --tags --abbrev=0 2>/dev/null || echo "No previous releases"`
-- Package version: @package.json or @setup.py or @pyproject.toml or @go.mod (if exists)
-- Unreleased changes: !`git log $(git describe --tags --abbrev=0)..HEAD --oneline 2>/dev/null | wc -l || echo "All commits"`
-- Branch status: !`git status --porcelain | wc -l || echo "0"` uncommitted changes
-- Build status: !`npm test 2>/dev/null || python -m pytest 2>/dev/null || go test ./... 2>/dev/null || echo "Test framework detection needed"`
-
-## Task
-
-Systematic release preparation: $ARGUMENTS
-
-1. **Release Planning and Validation**
-   - Determine release version number (semantic versioning)
-   - Review and validate all features included in release
-   - Check that all planned issues and features are complete
-   - Verify release criteria and acceptance requirements
-
-2. **Pre-Release Checklist**
-   - Ensure all tests are passing (unit, integration, E2E)
-   - Verify code coverage meets project standards
-   - Complete security vulnerability scanning
-   - Perform performance testing and validation
-   - Review and approve all pending pull requests
-
-3. **Version Management**
-   ```bash
-   # Check current version
-   git describe --tags --abbrev=0
-   
-   # Determine next version (semantic versioning)
-   # MAJOR.MINOR.PATCH
-   # MAJOR: Breaking changes
-   # MINOR: New features (backward compatible)
-   # PATCH: Bug fixes (backward compatible)
-   
-   # Example version updates
-   # 1.2.3 -> 1.2.4 (patch)
-   # 1.2.3 -> 1.3.0 (minor)
-   # 1.2.3 -> 2.0.0 (major)
-   ```
-
-4. **Code Freeze and Branch Management**
-   ```bash
-   # Create release branch from main
-   git checkout main
-   git pull origin main
-   git checkout -b release/v1.2.3
-   
-   # Alternative: Use main branch directly for smaller releases
-   # Ensure no new features are merged during release process
-   ```
-
-5. **Version Number Updates**
-   - Update package.json, setup.py, or equivalent version files
-   - Update version in application configuration
-   - Update version in documentation and README
-   - Update API version if applicable
-
-   ```bash
-   # Node.js projects
-   npm version patch  # or minor, major
-   
-   # Python projects
-   # Update version in setup.py, __init__.py, or pyproject.toml
-   
-   # Manual version update
-   sed -i 's/"version": "1.2.2"/"version": "1.2.3"/' package.json
-   ```
-
-6. **Changelog Generation**
-   ```markdown
-   # CHANGELOG.md
-   
-   ## [1.2.3] - 2024-01-15
-   
-   ### Added
-   - New user authentication system
-   - Dark mode support for UI
-   - API rate limiting functionality
-   
-   ### Changed
-   - Improved database query performance
-   - Updated user interface design
-   - Enhanced error handling
-   
-   ### Fixed
-   - Fixed memory leak in background tasks
-   - Resolved issue with file upload validation
-   - Fixed timezone handling in date calculations
-   
-   ### Security
-   - Updated dependencies with security patches
-   - Improved input validation and sanitization
-   ```
-
-7. **Documentation Updates**
-   - Update API documentation with new endpoints
-   - Revise user documentation and guides
-   - Update installation and deployment instructions
-   - Review and update README.md
-   - Update migration guides if needed
-
-8. **Dependency Management**
-   ```bash
-   # Update and audit dependencies
-   npm audit fix
-   npm update
-   
-   # Python
-   pip-audit
-   pip freeze > requirements.txt
-   
-   # Review security vulnerabilities
-   npm audit
-   snyk test
-   ```
-
-9. **Build and Artifact Generation**
-   ```bash
-   # Clean build environment
-   npm run clean
-   rm -rf dist/ build/
-   
-   # Build production artifacts
-   npm run build
-   
-   # Verify build artifacts
-   ls -la dist/
-   
-   # Test built artifacts
-   npm run test:build
-   ```
-
-10. **Testing and Quality Assurance**
-    - Run comprehensive test suite
-    - Perform manual testing of critical features
-    - Execute regression testing
-    - Conduct user acceptance testing
-    - Validate in staging environment
-
-    ```bash
-    # Run all tests
-    npm test
-    npm run test:integration
-    npm run test:e2e
-    
-    # Check code coverage
-    npm run test:coverage
-    
-    # Performance testing
-    npm run test:performance
-    ```
-
-11. **Security and Compliance Verification**
-    - Run security scans and penetration testing
-    - Verify compliance with security standards
-    - Check for exposed secrets or credentials
-    - Validate data protection and privacy measures
-
-12. **Release Notes Preparation**
-    ```markdown
-    # Release Notes v1.2.3
-    
-    ## 🎉 What's New
-    - **Dark Mode**: Users can now switch to dark mode in settings
-    - **Enhanced Security**: Improved authentication with 2FA support
-    - **Performance**: 40% faster page load times
-    
-    ## 🔧 Improvements
-    - Better error messages for form validation
-    - Improved mobile responsiveness
-    - Enhanced accessibility features
-    
-    ## 🐛 Bug Fixes
-    - Fixed issue with file downloads in Safari
-    - Resolved memory leak in background tasks
-    - Fixed timezone display issues
-    
-    ## 📚 Documentation
-    - Updated API documentation
-    - New user onboarding guide
-    - Enhanced troubleshooting section
-    
-    ## 🔄 Migration Guide
-    - No breaking changes in this release
-    - Automatic database migrations included
-    - See [Migration Guide](link) for details
-    ```
-
-13. **Release Tagging and Versioning**
-    ```bash
-    # Create annotated tag
-    git add .
-    git commit -m "chore: prepare release v1.2.3"
-    git tag -a v1.2.3 -m "Release version 1.2.3
-    
-    Features:
-    - Dark mode support
-    - Enhanced authentication
-    
-    Bug fixes:
-    - Fixed file upload issues
-    - Resolved memory leaks"
-    
-    # Push tag to remote
-    git push origin v1.2.3
-    git push origin release/v1.2.3
-    ```
-
-14. **Deployment Preparation**
-    - Prepare deployment scripts and configurations
-    - Update environment variables and secrets
-    - Plan deployment strategy (blue-green, rolling, canary)
-    - Set up monitoring and alerting for release
-    - Prepare rollback procedures
-
-15. **Staging Environment Validation**
-    ```bash
-    # Deploy to staging
-    ./deploy-staging.sh v1.2.3
-    
-    # Run smoke tests
-    npm run test:smoke:staging
-    
-    # Manual validation checklist
-    # [ ] User login/logout
-    # [ ] Core functionality
-    # [ ] New features
-    # [ ] Performance metrics
-    # [ ] Security checks
-    ```
-
-16. **Production Deployment Planning**
-    - Schedule deployment window
-    - Notify stakeholders and users
-    - Prepare maintenance mode if needed
-    - Set up deployment monitoring
-    - Plan communication strategy
-
-17. **Release Automation Setup**
-    ```yaml
-    # GitHub Actions Release Workflow
-    name: Release
-    
-    on:
-      push:
-        tags:
-          - 'v*'
-    
-    jobs:
-      release:
-        runs-on: ubuntu-latest
-        steps:
-          - uses: actions/checkout@v3
-          - name: Setup Node.js
-            uses: actions/setup-node@v3
-            with:
-              node-version: '18'
-          
-          - name: Install dependencies
-            run: npm ci
-          
-          - name: Run tests
-            run: npm test
-          
-          - name: Build
-            run: npm run build
-          
-          - name: Create Release
-            uses: actions/create-release@v1
-            env:
-              GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-            with:
-              tag_name: ${{ github.ref }}
-              release_name: Release ${{ github.ref }}
-              draft: false
-              prerelease: false
-    ```
-
-18. **Communication and Announcements**
-    - Prepare release announcement
-    - Update status page and documentation
-    - Notify customers and users
-    - Share on relevant communication channels
-    - Update social media and marketing materials
-
-19. **Post-Release Monitoring**
-    - Monitor application performance and errors
-    - Track user adoption of new features
-    - Monitor system metrics and alerts
-    - Collect user feedback and issues
-    - Prepare hotfix procedures if needed
-
-20. **Release Retrospective**
-    - Document lessons learned
-    - Review release process effectiveness
-    - Identify improvement opportunities
-    - Update release procedures
-    - Plan for next release cycle
-
-**Release Types and Considerations:**
-
-**Patch Release (1.2.3 → 1.2.4):**
-- Bug fixes only
-- No new features
-- Minimal testing required
-- Quick deployment
-
-**Minor Release (1.2.3 → 1.3.0):**
-- New features (backward compatible)
-- Enhanced functionality
-- Comprehensive testing
-- User communication needed
-
-**Major Release (1.2.3 → 2.0.0):**
-- Breaking changes
-- Significant new features
-- Migration guide required
-- Extended testing period
-- User training and support
-
-**Hotfix Release:**
-```bash
-# Emergency hotfix process
-git checkout main
-git pull origin main
-git checkout -b hotfix/critical-bug-fix
-
-# Make minimal fix
-git add .
-git commit -m "hotfix: fix critical security vulnerability"
-
-# Fast-track testing and deployment
-npm test
-git tag -a v1.2.4-hotfix.1 -m "Hotfix for critical security issue"
-git push origin hotfix/critical-bug-fix
-git push origin v1.2.4-hotfix.1
-```
-
-Remember to:
-- Test everything thoroughly before release
-- Communicate clearly with all stakeholders
-- Have rollback procedures ready
-- Monitor the release closely after deployment
-- Document everything for future releases