Files
Dani 054c0e56e9 fix(commands): Remove deprecated 'model: sonnet' field from 142 command files
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>
2025-10-21 10:08:58 -04:00

57 lines
1.3 KiB
Markdown

---
allowed-tools: Read, Edit, Bash
argument-hint: [workflow-name]
description: Execute GitHub Actions locally using act
---
# Act - GitHub Actions Local Execution
Execute GitHub Actions workflows locally using act: $ARGUMENTS
## Current Workflows
- Available workflows: !`find .github/workflows -name "*.yml" -o -name "*.yaml" | head -10`
- Act configuration: @.actrc (if exists)
- Docker status: !`docker --version`
## Task
Execute GitHub Actions workflow locally:
1. **Setup Verification**
- Ensure act is installed: `act --version`
- Verify Docker is running
- Check available workflows in `.github/workflows/`
2. **Workflow Selection**
- If workflow specified: Run specific workflow `$ARGUMENTS`
- If no workflow: List all available workflows
- Check workflow triggers and events
3. **Local Execution**
- Run workflow with appropriate flags
- Use secrets from `.env` or `.secrets`
- Handle platform-specific runners
- Monitor execution and logs
4. **Debugging Support**
- Use `--verbose` for detailed output
- Use `--dry-run` for testing
- Use `--list` to show available actions
## Example Commands
```bash
# List all workflows
act --list
# Run specific workflow
act workflow_dispatch -W .github/workflows/$ARGUMENTS.yml
# Run with secrets
act --secret-file .env
# Debug mode
act --verbose --dry-run
```