coding-agent

Files (1)

• SKILL.md

SKILL.md (first lines)

# Coding Agent (background-first)

Use the **`process` tool** for non-interactive coding work. This gives you
non-blocking execution, progress monitoring, stdin/stdout access, and clean
lifecycle management.

## The Pattern: workdir + process:start

```bash
# Start agent in a focused directory ("little box" — only sees relevant files)
process action:start command:"claude --dangerously-skip-permissions --print 'Your task'" workdir:~/project/folder
# Returns session_id immediately

# Monitor output
process action:log session_id:XXX lines:50

# Check if done
process action:poll session_id:XXX

# Send input (if agent asks a question)
process action:write session_id:XXX data:"y\n"

# Kill if needed
process action:kill session_id:XXX

# See all running agents
process action:list
```

**Why workdir matters:** Agent wakes up in a focused directory — doesn't wander
off reading unrelated files. Use `mktemp -d` for scratch/chat work.

---

## Claude Code

```bash
# Non-interactive (recommended for background tasks)
process action:start \
  command:"claude --print --output-format json --dangerously-skip-permissions 'Your task'" \
  workdir:~/project

# With worktree isolation
process action:start \
  command:"claude -w fix-issue-42 --print --output-format json --dangerously-skip-permissions 'Fix issue #42'" \
  workdir:~/project

# Parse JSON output from action:log once done
# { "result": "...", "session_id": "...", "total_cost_usd": ... }
```

---

## Codex CLI

```bash
# --full-auto: sandboxed but auto-approves in workspace
process action:start command:"codex exec --full-auto \"Build a snake game with dark theme\"" workdir:~/project

# --yolo: NO sandbox, NO approvals (fastest, most dangerous)
process action:start command:"codex --yolo \"Build a snake game with dark theme\"" workdir:~/project
```

---

## OpenCode

```bash
process action:start command:"opencode run 'Your task'" workdir:~/project
```

---

## PR Reviews

**⚠️ Never review PRs in the live assistant repo — clone to /tmp or use git worktree!**

```bash
# Option 1: Review in the actual project repo
process action:start command:"claude --print --dangerously-skip-permissions 'Review PR #42: git diff origin/main...origin/pr/42'" workdir:~/project

# Option 2: Clone to temp folder (safe for any repo)
REVIEW_DIR=$(mktemp -d)
git clone https://github.com/user/repo.git $REVIEW_DIR
cd $REVIEW_DIR && gh pr checkout 42
process action:start command:"claude --print --dangerously-skip-permissions 'Review this PR against main'" workdir:$REVIEW_DIR

# Option 3: Git worktree (keeps main intact)
git worktree add /tmp/pr-42-review pr-42-branch
process action:start command:"claude --print --dangerously-skip-permissions 'Review this PR'" workdir:/tmp/pr-42-review
```

### Batch PR Reviews (parallel army!)

```bash
# Fetch all PR refs
git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'

# Launch one agent per PR
process action:start command:"claude --print --dangerously-skip-permissions 'Review PR #86: git diff origin/main...origin/pr/86'" workdir:~/project
process action:start command:"claude --print --dangerously-skip-permissions 'Review PR #87: git diff origin/main...origin/pr/87'" workdir:~/project
process action:start command:"claude --print --dangerously-skip-permissions 'Review PR #95: git diff origin/main...origin/pr/95'" workdir:~/project

# Monitor all
process action:list

# Get result and post to GitHub
process action:log session_id:XXX
gh pr comment 86 --body "<review content>"
```

---

## Parallel Issue Fixing with git worktrees

```bash
# Create isolated worktrees per issue
git worktree add -b fix/issue-78 /tmp/issue-78 main
git worktree add -b fix/issue-99 /tmp/issue-99 main

From cedricziel/assistant, MIT.

More from cedricziel/assistant