let5see/clawdbot
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

coding-agent: comprehensive update from Jan 2 learnings

Browse Source 
- workdir 'little box' pattern (don't read unrelated files)
- background mode replaces tmux
- --full-auto for building, vanilla for reviewing
- parallel Codex processes supported
- PR review tips (fetch refs, use git diff, don't checkout)
- patience rules (don't kill slow sessions!)
This commit is contained in:
Peter Steinberger
2026-01-03 00:11:21 +00:00
parent b313250638
commit 1354d0836f
1 changed files with 34 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

43
skills/coding-agent/SKILL.md
View File

@@ -1,12 +1,12 @@
---
name: coding-agent
description: Run Claude Code, Codex CLI, or OpenCode via background process for programmatic control.
description: Run Codex CLI, Claude Code, or OpenCode via background process for programmatic control.
metadata: {"clawdis":{"emoji":"🧩","requires":{"anyBins":["claude","codex","opencode"]}}}
---
# Coding Agent (background-first)
Use **bash background mode** for all coding-agent CLIs. Full programmatic control, no tmux needed.
Use **bash background mode** for coding agents. Full programmatic control, no tmux needed.
## The Pattern: workdir + background
@@ -18,7 +18,7 @@ bash workdir:~/project/folder background:true command:"<agent command>"
# Monitor progress
process action:log sessionId:XXX
# Check if done
# Check if done
process action:poll sessionId:XXX
# Send input (if agent asks a question)
@@ -28,21 +28,44 @@ process action:write sessionId:XXX data:"y"
process action:kill sessionId:XXX
```
Why workdir matters: Agent wakes up in a focused directory, doesn't wander off reading unrelated files.
**Why workdir matters:** Agent wakes up in a focused directory, doesn't wander off reading unrelated files (like your soul.md 😅).
---
## Codex CLI
**Model:** `gpt-5.2-codex` — choose reasoning effort based on task:
- `medium` — most tasks
**Model:** `gpt-5.2-codex` is the default (set in ~/.codex/config.toml)
**Reasoning effort:** Choose based on task complexity:
- `medium` — most tasks (default)
- `high` — complex/architectural tasks
### Building/Creating (use --full-auto)
```bash
bash workdir:~/project background:true command:"codex exec --model gpt-5.2-codex -c reasoning_effort=\"medium\" -s workspace-write \"Your task\""
bash workdir:~/project background:true command:"codex exec --full-auto \"Build a snake game with dark theme\""
```
**Flags:** `-s workspace-write`, `--full-auto`, `--skip-git-repo-check`
### Reviewing (vanilla, no flags needed)
```bash
bash workdir:~/project background:true command:"codex exec \"Review PR #115. Run git diff origin/main...origin/pr/115 to see changes.\""
```
### Running Multiple Codex Processes
You can run many Codex processes in parallel! Each gets its own session:
```bash
# Start multiple reviews
bash workdir:~/project background:true command:"codex exec \"Review PR #1\""
bash workdir:~/project background:true command:"codex exec \"Review PR #2\""
bash workdir:~/project background:true command:"codex exec \"Review PR #3\""
# Check all running
process action:list
```
### PR Review Tips
- Fetch PR refs first: `git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'`
- Tell Codex to use: `git diff origin/main...origin/pr/XX`
- Don't let it checkout branches (conflicts with parallel reviews)
---
@@ -64,6 +87,8 @@ bash workdir:~/project background:true command:"opencode run \"Your task\""
## ⚠️ Rules
1. **Respect tool choice** — if user asks for Codex, use Codex. Don't offer to build it yourself!
1. **Respect tool choice** — if user asks for Codex, use Codex. NEVER offer to build it yourself!
2. **Be patient** — don't kill sessions because they're "slow"
3. **Monitor with process:log** — check progress without interfering
4. **--full-auto for building** — auto-approves changes
5. **vanilla for reviewing** — no special flags needed