commandcode-delegate
Delegate a coding task to the Command Code CLI (`cmd`) as a background implementer, then review its diff and land it yourself.
Install / Use
npx skills add amElnagdy/delegate-skills --skill commandcode-delegateInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of commandcode-delegate
commandcode-delegate scores 89/100 on our quality scale, 1599th of 4,698 Development & Engineering skills we index (top 35%).
Its SKILL.md is 10 KB long, well organised into 18 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 2,181 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so commandcode-delegate is actively maintained.
- Our last check on 2026-10-31 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
ReviewOur scan of the whole file found 1 pattern worth reviewing before you install commandcode-delegate. An AI review judged it risky: The relay helper defaults to `--yolo` (`--dangerously-skip-permissions`), which disables Command Code CLI permission prompts for writes, edits, and shell calls.
- mediumDisables the agent's permission promptsline 42
- **`--yolo` (alias `--dangerously-skip-permissions`):** every tool is allowed, anywhere the process
AI review: risky
- The relay helper defaults to `--yolo` (`--dangerously-skip-permissions`), which disables Command Code CLI permission prompts for writes, edits, and shell calls.
- It instructs the orchestrating agent to run full-trust implementation runs that can edit the working tree and execute shell commands without per-action approval.
- While it is a legitimate delegation workflow, the default bypass of permission safeguards meaningfully weakens the agent's safeguards.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
commandcode-delegate compared with similar skills
All 4 of these similar skills score higher than commandcode-delegate; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| commandcode-delegate (this skill)by amElnagdy | 89 | 2.2k | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP Server |
Frequently asked questions
- How do I install commandcode-delegate?
- Run
npx skills add amElnagdy/delegate-skills --skill commandcode-delegate. The install tabs above show the steps for each supported agent. - Which AI agents does commandcode-delegate work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is commandcode-delegate safe to use?
- Our scan of the whole file found 1 pattern worth reviewing before you install commandcode-delegate. An AI review judged it risky: The relay helper defaults to
--yolo(--dangerously-skip-permissions), which disables Command Code CLI permission prompts for writes, edits, and shell calls. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand. - Is commandcode-delegate still maintained?
- The repository was last updated about 2 months ago, so commandcode-delegate is actively maintained.
Skill content
View source on GitHubname: commandcode-delegate
description: >-
Delegate a coding task to the Command Code CLI (cmd) as a background implementer, then review its
diff and land it yourself. Use this whenever the user wants to hand implementation work to Command
Code — phrasings like "have Command Code do X", "delegate this to commandcode", "run it through
cmd", or "use Command Code to implement/fix/refactor" — or to run a queue of coding tasks through
Command Code while staying the reviewer. DO NOT USE for tasks small enough to do inline, or when the
user wants the code written directly without delegating.
license: MIT
compatibility: Requires the Command Code CLI (cmd, or cmdc on Windows, from commandcode.ai) installed and authenticated, Node 22+, and git. The orchestrating agent must be able to run shell commands and read files. Shell examples assume bash/zsh (macOS/Linux).
metadata:
version: 0.5.0
Command Code Delegate
You are the orchestrator. This skill lets you hand a bounded coding task to a separate
implementer — the Command Code CLI (cmd) — then review what it produced and land it yourself.
You write the brief and own the judgment; Command Code does the typing in your working tree; 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 it works the same whether you are Claude Code, OpenCode with a selected model, or any comparable agent. (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
cmdCLI is not installed or not authenticated (runcmd login). - You want to write the code yourself, or you only need a review (Command Code has its own
/review). - You are on native Windows and
cmdc --versiondoes not work. Upstream recommends WSL for stable Windows use.
Read this before the first dispatch: the autonomy model
Command Code's headless mode has exactly two states, with nothing in between:
- Default (
-pwith no--yolo): read, grep, and glob work. Every write, edit, and shell call is refused by the CLI's permission layer, and headless mode has no prompt to grant them mid-run. This is the relay's--read-only. --yolo(alias--dangerously-skip-permissions): every tool is allowed, anywhere the process can reach. There is no filesystem sandbox and no path restriction. This is what an implementation run needs, so the relay passes it by default.
--permission-mode auto-accept and --tools-all do not lift the headless write gate. Direct CLI
probes refused write, edit, and shell with both. So an implementation run
through Command Code is a full-trust run: scope it with a tight brief and a clean working tree, not
with a sandbox. The brief is guidance, and a git worktree isolates a checkout without containing the
process. If writes outside the target tree are unacceptable, use an OS-enforced sandbox such as
codex-delegate or run this one inside a container.
Prerequisites (check once)
cmd --versionsucceeds andcmd statusreports authenticated. If not, install Command Code and runcmd login.- Confirm the CLI on PATH. On macOS/Linux,
command -v cmdshows the activecmd. On native Windows, usecmdc --version;cmdis the system shell. The relay usescmdcthere and launches its npm.cmdshim throughcmd.exe.COMMANDCODE_BINremains an absolute-path override and must never point to the system command interpreter. The relay records the version it ran inresult.json, so a wrong binary is visible after the fact. - You are in (or will point
--cdat) the target git repository, and its tree is clean before you dispatch — a full-trust run is much easier to review against a clean baseline.
The loop
Run these five steps per task. Steps 1, 4, and 5 are your judgment; 2 and 3 are mechanical.
1. Write the brief
Command Code sees only the text you send — no repo memory, no chat history, no shared context
(beyond the repo's own AGENTS.md, which it reads automatically). Everything the task needs goes in
the brief: the goal, the current state, what to change, what to leave untouched, the project's
actual gate commands (discover them from the repo's AGENTS.md/CLAUDE.md/Makefile — do not assume),
and a report contract. Tell it that it will not commit (you will). Keep one task per brief. Full
guidance and a template: references/writing-the-brief.md.
2. Dispatch
Send the brief to Command Code with the bundled helper. It wraps cmd -p, captures the run, and
writes a structured result.json — so your only job is "run a command, read a file." (<skill-dir>
below is this skill's installed directory — the folder containing this SKILL.md, i.e. the directory
you loaded the skill from. Claude Code prints it as "Base directory for this skill" when the skill
loads; on other orchestrators use that same directory — if unsure where it landed, run
find ~ -name relay.mjs -path '*commandcode-delegate*' and substitute the directory above it.)
node "<skill-dir>/scripts/relay.mjs" --brief brief.txt --cd /path/to/repo
# read-only (review/diagnosis, no edits): add --read-only
# continue the exact session: add --session <sessionId> (from result.json; send only the delta brief)
# fallback when no session id is available: add --continue-last
# hard time limit (watchdog): add --timeout 2h (default: off; implementation runs routinely need 1-2h)
# see all options: node .../relay.mjs --help
The helper defaults to a write-capable (--yolo) run, which intentionally edits the target repository.
Its temp directory keeps only relay artifacts out of that repository. The relay never commits —
see step 5. Mechanics, flags, and the
result.json shape: references/dispatch-and-poll.md.
3. Wait for completion
The helper blocks until Command Code finishes, so back it with whatever your orchestrator offers and resume when it returns:
- Claude Code: run the Bash call with
run_in_background: true; you are notified on completion. - Plain shell / other agents: run it in the foreground for short tasks, or background it and poll
the result file —
… &in bash/zsh, or your shell's equivalent. The run is done whenresult.jsonexists with astatus. (A pre-run usage error — bad args or an empty brief — instead exits with code 2 and a stderr message and writes no result file, so check the exit code too. A missingcmdbinary exits 127 but does write aresult.jsonwith statuscommandcode_unavailable.)
Do not trust progress trackers over reality: a run is finished when result.json is written and the
process has exited. Read the working tree, not a status line. The implementer's full report is the
finalMessage field in result.json (also printed in full on stdout between the report markers).
4. Review — do not trust the self-report
result.json includes Command Code's own summary and gate claims. Re-verify, don't accept:
- Re-run the project's gates yourself (the test/lint/build commands from step 1). Never take "gates passed" on faith.
- Read the diff against the brief: did it do what was asked, nothing more (scope creep) and
nothing less?
touchedFilesin the result is your starting point — and because the run was full-trust, check for edits outside the paths the brief named, not just inside them. - Run the relevant guard skills on the diff if you have them installed (clean-code-guard,
test-guard, etc. from
guard-skills) — this skill produces the work; those skills judge it. - For schema/migration changes, round-trip them; for removals, grep for dangling references.
Full checklist: references/review-and-land.md.
5. Land it
The relay never commits, but it cannot stop Command Code under --yolo from writing .git. The brief
forbids implementer commits, and the reviewer compares HEAD with the recorded pre-dispatch baseline
before landing anything. The orchestrator commits. Only after the gates pass and the diff holds:
- Commit the verified work yourself, with a clear message.
- If it needs changes, send a delta brief with
--session <sessionId>from the priorresult.json(use--continue-lastonly when no session id is available), and review again.
Read-only second opinions
The relay doubles as a clean way to get an adversarial second opinion: dispatch --read-only with a
brief that lists the agreed points, then each contested point with both positions, and ask Command
Code to defend or concede each — deliverable in its final message, touching no files. The read-only
guarantee here is the CLI's own permission layer rather than an OS sandbox, so the relay also checks
it after the fact: readOnlyViolation: false means the Git-visible detector saw no change (ignored
or outside-repository paths are not covered); true means it saw one; null means git could not tell.
Authorization model
Delegation is something the human opts into. Once they have ("run this queue", "proceed"), committing verified, gate-passing work is the agreed contract — that is the whole point. Two limits on that mandate: surface, don't absorb (report Command Code's design decisions, defensible-but-unasked turns, and non-blocking nitpicks rather than silently keeping them) and stop for scope changes (if correct completion needs going beyond the brief, ask — don't expand the mandate yourself). The full treatment is in references/review-and-land.md.
References
- references/writing-the-brief.md — how to write a brief Command Code can execute blind: structure, XML blocks, the report contract, embedding the real gate commands.
- references/dispatch-and-poll.md —
relay.mjsflags, theresult.jsoncontract, backgrounding per orchestrator, and recovery when a run misbehaves. - references/review-and-land.md — the review checklist, the commit boundary, and the exact-session rework cycle.
- references/multi-task-queues.md — running a sequential queue: carrying constraints forward, progress tracking, and the end-of-run coherence check.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
