claude-code-orchestrator-kit

🎼 Turn Claude Code into a production powerhouse. 33+ AI agents automate bug fixing, security scanning, and dependency management. 19 slash commands, 6 MCP configs (600-5000 tokens), quality gates, and health monitoring. Ship faster, ship safer, ship smarter.

[{"step":1,"action":"Initialize the orchestrator in your project root. Run: `claude-code-orchestrator-kit init` and select your tech stack (Node.js, Python, etc.). This generates a `.claude-orchestrator/` directory with MCP configs and slash command templates.","tip":"Use `/init --preset=full` for the most comprehensive setup, including security scanning and dependency management."},{"step":2,"action":"Define your workflow in `workflows.json`. Example: `{ \"name\": \"nightly-build\", \"steps\": [\"update-deps\", \"security-scan\", \"run-tests\", \"deploy-staging\"] }`.","tip":"Leverage the 19 built-in slash commands (e.g., `/update-deps`, `/security-scan`) to avoid writing custom scripts. Use `--auto-approve` for non-critical steps."},{"step":3,"action":"Set up quality gates in `quality-gates.toml`. Configure thresholds for test coverage, linting errors, and security scores. Example: `[coverage] minimum = 85` or `[security] max_critical = 0`.","tip":"Run `/health-check --dry-run` to simulate the workflow and validate gate configurations before execution."},{"step":4,"action":"Trigger the workflow manually or via CI. Use `/orchestrate --workflow=nightly-build` or integrate with GitHub Actions using the `claude-code-orchestrator-action`.","tip":"Monitor progress in real-time via the built-in dashboard (accessible at `http://localhost:3000/orchestrator`). Use `/logs --tail=50` to fetch recent logs."},{"step":5,"action":"Review the final report and act on failures. Use `/rollback --last-deploy` if the deployment fails quality gates. Investigate agent logs for root causes.","tip":"Enable MCP health monitoring (`mcp-health-monitor.toml`) to receive Slack/email alerts for agent failures or resource constraints."}]