Create worktree + spawn agent
Description
git worktree add ../feat-custom-templates -b feat/custom-templates origin/main cd ../feat-custom-templates && pnpm install tmux new-session -d -s "codex-templates" \ -c "/Users/elvis/Documents/GitHub/
Installation
claude install-skill https://github.com/LKbaba/Claude-code-ChatInWindows README
要查看键盘快捷键,按下问号 查看键盘快捷键
文章
查看新帖子 对话 Elvis @elvissun OpenClaw + Codex/ClaudeCode Agent Swarm: The One-Person Dev Team [Full Setup] I don't use Codex or Claude Code directly anymore. I use OpenClaw as my orchestration layer. My orchestrator, Zoe, spawns the agents, writes their prompts, picks the right model for each task, monitors progress, and pings me on Telegram when PRs are ready to merge. Proof points from the last 4 weeks:
- undefined
Codex and Claude Code have very little context about your business. They see code. They don't see the full picture of your business. OpenClaw changes the equation. It acts as the orchestration layer between you and all agents — it holds all my business context (customer data, meeting notes, past decisions, what worked, what failed) inside my Obsidian vault, and translates historical context into precise prompts for each coding agent. The agents stay focused on code. The orchestrator stays at the high strategy level. Here's how the system works at a high level: Last week Stripe wrote about their background agent system called "Minions" — parallel coding agents backed by a centralized orchestration layer. I accidentally built the same thing but it runs locally on my Mac mini. Before I tell you how to set this up, you should know WHY you need an agent orchestrator. Why One AI Can't Do Both Context windows are zero-sum. You have to choose what goes in. Fill it with code → no room for business context. Fill it with customer history → no room for the codebase. This is why the two-tier system works: each AI is loaded with exactly what it needs. OpenClaw and Codex have drastically different context: Specialization through context, not through different models. The Full 8-step Workflow Let me walk through a real example from last week. Step 1: Customer Request → Scoping with Zoe I had a call with an agency customer. They wanted to reuse configurations they've already set up across the team. After the call, I talked through the request with Zoe. Because all my meeting notes sync automatically
Related Skills
使用 Git Worktrees
创建孤立的 Git worktrees,带有智能目录选择与安全验证。
Git community Claude skills github
[Building agent skills blog](https://www.anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills)
Git community #148
, [#161](https://github.com/affaan-m/everything-claude-code/pull/161))
Git community GitHub MCP
| Token | Repos, issues, PRs, workflows |
Git community GitHub MCP Server
Official first-party server to read repos, manage issues/PRs, and automate workflows.
Git community mcp-server-github
GitHub API integration for repos, issues, PRs.
Git community