Skills

Opencode Delegate

Delegate a coding task to the OpenCode CLI as a background implementer, then review its...

Install

npx skills add amElnagdy/delegate-skills --skill opencode-delegate -g -a claude-code -y
Category
Git and review
Updated
6d ago
License
MIT
Context cost
Mediumabout 2,611 tokens
Runs scripts
Yes, review before use

What it does

Delegate a coding task to the OpenCode CLI as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to hand implementation work to OpenCode, phrasings like "have OpenCode do X", "delegate this to OpenCode", "run it through OpenCode", or "use OpenCode to implement/fix/refactor", or wants to run a queue of coding tasks through OpenCode while staying the reviewer. Prefer it when the user will review the diff and commit it themselves. DO NOT USE for tasks small enough to do inline, or when the user wants the code written directly without delegating.

OpenCode Delegate

You are the orchestrator. This skill lets you hand a bounded coding task to a separate implementer, the OpenCode CLI, then review what it produced and land it yourself. You write the brief and own the judgment; OpenCode does the typing in its own session; you verify and commit.

Nothing here is specific to one orchestrating agent. The loop needs only the ability to run a shell command and read a file, so any agent with those two capabilities, Claude Code, OpenCode driving a sibling session, or a comparable one, can drive it. (It is designed for and run on Claude Code; treat other orchestrators as designed-for, not yet proven.)

When NOT to use this

  • The task is small enough to just do inline, delegation overhead is not worth it.
  • The opencode CLI is not installed or not authenticated (run opencode auth login).
  • You want to write the code yourself, or you only need a review (use the plan agent via --read-only).

Prerequisites (check once)

  1. opencode --version succeeds. If not, install (npm i -g opencode-ai, or the native installer from opencode.ai) and opencode auth login.
  2. Confirm which opencode is on PATH. command -v opencode shows the active binary and opencode --version its version. The relay records the version it ran into result.json, so a stale binary is visible after the fact.
  3. A model provider is authenticated, opencode auth list shows at least one credential.
  4. You are in (or will point --cd at) the target git repository.

Choose the implementer model

OpenCode has no safe default, a bare opencode run errors, so a fresh run needs a model via --model or a fleet --lane that sets one (a resumed run inherits its session's model). Naming the model is the one decision a single-model backend like codex-delegate never had, and it has two owners:

Read the whole SKILL.md on GitHub

More in Git and review