Deploy the ExFabrica Agentic Factory applications to the specified environment with comprehensive validation and safety checks.
Deploy ExFabrica Agentic Factory applications with comprehensive validation, safety checks, and environment-specific workflows. Use for dev/staging/production deployments with optional test skipping and build controls.
/plugin marketplace add hubexab/EAF-PluginClaude/plugin install exfabrica-af-plugin@exfabrica-af-marketplaceDeploy the ExFabrica Agentic Factory applications to the specified environment with comprehensive validation and safety checks.
/deploy <environment> [--skip-tests] [--skip-build]
dev - Development environmentstaging - Staging/pre-production environmentproduction - Production environmentWhen you execute this command, Claude will:
Pre-deployment Validation
Quality Checks (unless --skip-tests is used)
yarn workspace @bdqt/backend test)yarn workspace @bdqt/frontend test)Build Process (unless --skip-build is used)
yarn workspace @bdqt/backend build)yarn workspace @bdqt/frontend build)Deployment Execution
Post-deployment
/deploy dev
Quick deployment to development environment with all validations.
/deploy staging
Deploy to staging environment with full test suite and smoke tests.
/deploy production
Deploy to production with maximum safety checks, explicit confirmation, and monitoring.
/deploy dev --skip-tests
Fast deployment to development when you're confident in your changes.
dev)staging)production)Before deploying, ensure:
Environment Configuration
.env.development, .env.staging, or .env.production file existsInfrastructure
Code Quality
Error: Tests failed - cannot proceed with deployment
Solution: Run /test-all to identify and fix failing tests.
Error: Build failed with TypeScript errors
Solution: Run /analyze-code to identify and fix type errors.
Error: Required environment variable DATABASE_URL not set
Solution: Check .env.{environment} file and ensure all required variables are present.
Error: Uncommitted changes detected
Solution: Commit or stash your changes before deploying.
/test-all - Run comprehensive test suite/analyze-code - Check code quality before deployment/db-operations migrate - Run database migrations manually/generate-api-client - Update API client before deploymentAlways test before deploying to production
/test-all
/deploy production
Use staging as a production mirror
/deploy staging
# Verify manually
/deploy production
Keep deployments small and frequent
Monitor after deployment
This command can trigger Azure DevOps pipelines if configured in your azure-pipelines.yml:
dev pipelinestaging pipelineproduction pipeline with approvalsThe command will wait for pipeline completion and report the results.
Note: This command respects the lifecycle hooks configured in config/hooks.json and will run pre-deployment and post-deployment hooks automatically.