Generalized guides for running Claude Code as the orchestration kernel for a multi-developer team, with GitHub for version control and Discord as the communication terminal.
These guides are distilled from real production use. Each one is standalone - read them in sequence for a full setup, or jump directly to the topic you need.
| # |
Guide |
What it covers |
| 1 |
Git Worktrees |
Parallel development with isolated worktrees, launcher scripts, naming conventions |
| 2 |
Conflict Resolution |
Three-layer system: prevent, detect, and resolve merge conflicts with Claude |
| # |
Guide |
What it covers |
| 3 |
Discord Hooks |
Webhook integration for PR events, reviews, approvals, and merges |
| 4 |
Permission Relay |
Forwarding Claude approval prompts to phone and Discord via --channels |
| # |
Guide |
What it covers |
| 5 |
Agent Teams |
Parallel review agents (logic, tests, performance, security) with team lead synthesis |
| 6 |
Custom Subagents |
Implementation and ops specialist agents with auto-invoke by keyword |
| 7 |
Multiclaude |
Evaluating Multiclaude for multiplayer code review alongside your custom system |
| # |
Guide |
What it covers |
| 8 |
Cloud Auto-Fix |
GitHub Actions workflow to auto-fix CI failures and green review items |
| 9 |
Scheduled Tasks |
VPS cron jobs for morning digest, stale PR detection, security audits, CI monitoring |
| # |
Guide |
What it covers |
| 10 |
Plan Mode |
When Claude plans before acting, the plan format, and enforcement by session type |
| # |
Guide |
What it covers |
| 11 |
Session Management |
CCManager vs Claude Squad evaluation, Haiku auto-approval, session recovery |
| 12 |
Plugins |
Plugin ecosystem, context budget rules, overlap analysis, evaluation cycle |
Before starting:
- Claude Code installed and authenticated (
claude --version)
- GitHub repo with branch protection on
main (require 1 approval before merge)
- Discord server with admin access (to create webhooks)
- VPS or server for scheduled tasks (optional but recommended)
gh CLI installed and authenticated
These guides are intentionally generic. If you have a process that works well for your Claude Code + GitHub + Discord setup, open a PR. Keep it generalized - no project-specific names, domains, or stack assumptions.
