Production-ready slash commands for Claude Code enable intelligent automation and multi-agent orchestration. Developers and operations teams use these commands to streamline workflows, connect tools, and improve productivity in software development.
git clone https://github.com/wshobson/commands.githttps://docs.anthropic.com/en/docs/claude-code
1. **Define the command purpose**: Start by identifying the specific automation task (e.g., deployments, backups, testing). Use clear, actionable verbs like `/deploy`, `/backup`, or `/test`. 2. **Add required parameters**: Include [PLACEHOLDERS] for critical inputs like `--env`, `--component`, or `--version`. Use `--help` to document optional flags (e.g., `--dry-run`). 3. **Implement idempotency**: Ensure the command can be rerun safely. For example, check if a deployment already exists before proceeding. 4. **Add error handling**: Include validation for inputs (e.g., invalid environment names) and graceful fallbacks (e.g., retrying failed steps). 5. **Log and document**: Save execution logs to a timestamped file and include a summary of actions taken. Use comments in the command to explain complex logic. Tip: Test commands in a `--dry-run` mode first to verify behavior without side effects.
Automate the implementation of OAuth2 authentication for secure user access.
Streamline CI/CD pipeline processes to enhance deployment efficiency.
Conduct comprehensive security scans to identify and remediate vulnerabilities.
Facilitate multi-agent code reviews to ensure quality and performance across projects.
No install command available. Check the GitHub repository for manual installation instructions.
git clone https://github.com/wshobson/commandsCopy the install command above and run it in your terminal.
Launch Claude Code, Cursor, or your preferred AI coding agent.
Use the prompt template or examples below to test the skill.
Adapt the skill to your specific use case and workflow.
Write a production-ready slash command for Claude Code to [TASK]. Use [TOOLS] if needed. Ensure the command is idempotent, handles errors gracefully, and includes logging. Example: '/deploy --env staging --component api --version 1.2.3'
Here’s a production-ready slash command for Claude Code to automate a database migration in a staging environment: ``` /command /migrate-db --env staging --schema updates/v2024.05.15 Executing migration for environment: staging Schema version: v2024.05.15 1. Checking database connection... ✅ 2. Validating schema files... ✅ 3. Running migrations... - Migrating table 'users'... ✅ - Adding column 'last_login'... ✅ - Creating index 'idx_email'... ✅ 4. Verifying migration integrity... ✅ Migration completed successfully in 42s. Log file saved to: /logs/migration-staging-20240515-1422.log Next steps: - Run smoke tests: /test --env staging --suite db - Promote to production: /promote --env prod --schema v2024.05.15 ``` The command includes: - Environment validation (staging/production) - Schema versioning for traceability - Step-by-step execution with status checks - Error handling for connection or schema issues - Logging for audit trails - Clear next steps for follow-up actions
Auto-transcribe meetings and generate action items
AI assistant built for thoughtful, nuanced conversation
IronCalc is a spreadsheet engine and ecosystem
Customer feedback management made simple
Enterprise workflow automation and service management platform
Automate your spreadsheet tasks with AI power
Take a free 3-minute scan and get personalized AI skill recommendations.
Take free scan