XSource
Thread: tips sourced from the Claude Code team
by Boris Cherny (@bcherny) · 2026-01-31
✓ Opened via the X API on 2026-10-15
Read the original ↗Part 1 · What the source did
The creator of Claude Code shared his team's habits: run 3–5 sessions in parallel worktrees, start complex work in plan mode, and turn anything you do daily into a skill.
- Runs several Claude sessions at once, each in its own worktree.
- Has one Claude write a plan and a second review it like a staff engineer.
- Turns repeated work into slash commands, such as a /techdebt sweep at the end of a session.
“Spin up 3–5 git worktrees at once”— Boris Cherny (@bcherny), X
Summary written by Agent Cookbook. See the original for the full context.
Part 2 · Our copy-paste version
Adapted by us from what the source described. Fill in the [BRACKETS].
The prompt
/techdebt (save as .claude/commands/techdebt.md):
Look only at files changed in this branch. Find duplicated code, dead code and copy-pasted helpers. List each with file:line and a proposed consolidation. Apply only the ones I tick.
🛡
Approval ruleCommands propose changes; you tick which to apply.
Set it up
- Create 3 worktrees and give each a separate task.
- Start each in plan mode; have a second session review the plan.
- Save the command above and run it before each PR.
Common failures
⚠
What usually goes wrong
- Too many sessions overloads your review capacity.
- Shared dev databases cause interference between worktrees.
Variations
- Keep a read-only analysis worktree.
- Add a command that gathers recent Slack, Drive and GitHub context.