PluginBench
Skill
Fail
Audit score 45

coding-agent

steipete/clawdis

Delegate coding work to background agents (Claude Code, Codex, OpenCode) for large refactors and feature builds.

What is coding-agent?

Spawn background coding agents to handle feature builds, PR reviews, large refactors, and issue-to-PR loops without blocking. Use for substantial work; not simple edits or read-only lookups. Requires Claude Code, Codex, or OpenCode CLI installed.

  • Launch Claude Code, Codex, or OpenCode as isolated background workers
  • Send task prompts via temp files to avoid shell quoting issues
  • Monitor worker progress and status with process commands (list, poll, log, kill)
  • Receive completion notifications via configurable channels (Slack, email, etc.)
  • Support long-running issue-to-PR workflows with durable GitHub issue specs
  • Create scratch git repos for Codex when needed

How to install coding-agent

npx skills add https://github.com/steipete/clawdis --skill coding-agent
Prerequisites
  • One of: Claude Code CLI (@anthropic-ai/claude-code), Codex CLI (@openai/codex), or OpenCode CLI installed
  • Notification channel configured (Slack, email, or other) for completion messages
  • Git repository for work (or ability to create scratch repos)
  • skills.entries.coding-agent.enabled in config
Claude Code
Cursor
Windsurf
Cline

How to use coding-agent

  1. 1.Write your task prompt to a temp file using mktemp
  2. 2.Append the notification block with channel, target, and account details
  3. 3.Launch the worker with background:true using bash command (codex exec, claude, or opencode run)
  4. 4.Capture and save the returned sessionId for monitoring
  5. 5.Monitor progress with process poll <sessionId> or process log <sessionId>
  6. 6.Receive completion message on your configured notification channel when done

Use cases

Good for
  • Delegate a multi-file refactor while you work on other tasks
  • Automate issue-to-PR loops: branch, implement, test, and open PR automatically
  • Run PR reviews as background workers to identify issues without blocking
  • Build new features in isolated checkouts and receive notifications when complete
  • Spawn multiple coding agents in parallel for independent tasks
Who it's for
  • Engineering teams automating code review and refactoring workflows
  • Developers managing large codebases who need parallel coding work
  • Teams using GitHub issues as durable specs for feature development
  • Users of Claude Code, Codex, or OpenCode CLI tools

coding-agent FAQ

When should I use this vs. making edits directly?

Use this for substantial work: multi-file refactors, feature builds, PR reviews, or issue-to-PR loops. Do not use for simple single-file edits, read-only code lookup, or work in active OpenClaw state directories.

What happens if the background worker hangs or fails?

Monitor with process commands. If it fails, respawn the worker or ask for clarification. Do not silently hand-code the work instead. Do not kill slow workers without cause.

Do I need to set up a notification channel?

Yes. Capture a real notification route (Slack, email, etc.) before spawning. Include it in the notification block so the worker can send completion messages. If no trustworthy route exists, notify the user that auto-notify is unavailable.

Can I run multiple coding agents in parallel?

Yes. Each worker is independent and runs in its own background session with a unique sessionId. Monitor each separately using process commands.

Why should I use a temp file for the prompt?

Temp files avoid shell quoting bugs when the notification block contains quotes or newlines. Write the prompt to a file first, then pass the file path to the agent command.

Full instructions (SKILL.md)

Source of truth, from steipete/clawdis.


name: coding-agent description: "Delegate coding work to Codex, Claude Code, or OpenCode as background workers; not simple edits or read-only code lookup." metadata: { "openclaw": { "emoji": "🧩", "requires": { "anyBins": ["claude", "codex", "opencode"], "config": ["skills.entries.coding-agent.enabled"], }, "install": [ { "id": "node-claude", "kind": "node", "package": "@anthropic-ai/claude-code", "bins": ["claude"], "label": "Install Claude Code CLI (npm)", }, { "id": "node-codex", "kind": "node", "package": "@openai/codex", "bins": ["codex"], "label": "Install Codex CLI (npm)", }, ], }, }

Coding Agent

Use for background feature builds, PR reviews, large refactors, and issue-to-PR loops. Do not use for simple edits, read-only lookup, ACP thread-bound work, or any run inside ~/.openclaw, $OPENCLAW_STATE_DIR, or active OpenClaw state dirs.

Hard rules

  • Always launch with background:true.
  • Codex and OpenCode: use pty:true.
  • Claude Code: no PTY; use claude --permission-mode bypassPermissions --print.
  • Capture a real notification route before spawning.
  • Worker must send completion/failure via openclaw message send.
  • Do not rely on heartbeat, system events, or notify-on-exit.
  • Monitor with process; do not kill slow workers without cause.
  • If user asked for a specific agent, use that agent.
  • If worker fails/hangs, respawn or ask; do not silently hand-code instead.
  • Never checkout branches or run background coding agents in ~/Projects/openclaw; use an isolated checkout.

Notification block

Append this shape to every worker prompt with real values:

Notification route:
- channel: <notifyChannel>
- target: <notifyTarget>
- account: <notifyAccount or omit>
- reply_to: <notifyReplyTo or omit>
- thread_id: <notifyThreadId or omit>

When finished, send exactly one completion or failure message using:
openclaw message send --channel <channel> --target '<target>' --message '<brief result>'
Add --account, --reply-to, or --thread-id only when present above.
Do not use openclaw system event or heartbeat.

If no trustworthy route exists, say completion auto-notify is unavailable.

Launch forms

Write the worker prompt to a temp file first. This avoids shell quoting bugs when the required notification block contains quotes or newlines.

PROMPT=$(mktemp -t openclaw-worker-prompt.XXXXXX)
cat >"$PROMPT" <<'EOF'
Task.
<notification block>
EOF
printf 'prompt file: %s\n' "$PROMPT"

Use $PROMPT when launching from the same shell/session. If using a separate tool call, substitute the printed path.

Codex:

bash pty:true background:true workdir:/path/repo command:"codex exec - < \"$PROMPT\""

Claude Code:

bash background:true workdir:/path/repo command:"claude --permission-mode bypassPermissions --print < \"$PROMPT\""

OpenCode:

bash pty:true background:true workdir:/path/repo command:"opencode run < \"$PROMPT\""

Long issue-to-PR work

  1. Create/reuse a GitHub issue as durable spec.
  2. Include issue URL, repo, base branch, expected PR, proof, and notification route.
  3. Tell worker to branch, implement, test, run review until no accepted actionable findings, open PR.
  4. Return issue URL and sessionId immediately.
  5. Monitor with process; cancel through Task Registry if mirrored there.

Scratch Codex

Codex needs a trusted git repo:

SCRATCH=$(mktemp -d)
git -C "$SCRATCH" init
PROMPT=$(mktemp -t openclaw-worker-prompt.XXXXXX)
cat >"$PROMPT" <<'EOF'
Build X.
<notification block>
EOF
printf 'prompt file: %s\n' "$PROMPT"
bash pty:true background:true workdir:$SCRATCH command:"codex exec - < \"$PROMPT\""

Process actions

  • list: running/recent sessions.
  • poll: status.
  • log: output.
  • submit: send input + Enter.
  • write: raw stdin.
  • paste: paste text.
  • kill: terminate.

Status to user

  • Say what started, where, and sessionId.
  • Update only on milestone, worker question, error, user action needed, or finish.
  • If killed, say why.