Route production coding tasks to the user-level Shell, TypeScript, Python, or Rust Codex workflow. Use for "codex-coder", "Codex write", "generate with Codex", language migrations, or mixed Shell/TypeScript/Python/Rust implementation when Codex should choose the correct language specialist automatically.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Carry the task's finite time budget into the coding assignment, including test time. Require a duration estimate before each targeted test run; full evaluation, unit, integration, or repository suites require the owner's explicit request, not dispatcher approval. New security checks require the owner's specific approval; auxiliary checks must not block the requested function or development work.
Act as a thin dispatcher. Select the language skill, then let that skill own repository discovery, prompting, implementation, verification, and refinement. Do not keep a second copy of language rules here.
Keep the owner's configured sandbox_mode = "danger-full-access"; do not override it
in a dispatch, config, flag, or profile. A connection or credential error does not identify
its cause. Inspect the effective configuration, actual endpoint, and error; repair the
observed cause within existing authority. Preserve valid results from unaffected tests.
Use this precedence order:
Ask one concise clarification only when those signals still do not identify the destination. Do not infer a language from personal preference or tool availability.
| Destination | Strong signals | Required skill |
|---|---|---|
| Bash or shell | .sh, a Bash shebang, shell CLI, automation, process wrapper, or Git/infra helper | $shellscript-coder |
| TypeScript or TSX | .ts, .tsx, .mts, .cts, tsconfig.json, a typed Node or React target | $ts-coder |
| Python | .py, pyproject.toml, Python service, package, script, or test target | $python-coder |
| Rust | .rs, Cargo.toml, Cargo workspace, crate, Rust CLI, service, library, or FFI target | $rust-coder |
JavaScript without a TypeScript target is not automatically TypeScript. An unsupported destination must be surfaced instead of silently routed to the nearest skill.
Resolve the user-level skill root as ${CODEX_HOME:-$HOME/.codex}/skills. For every selected language:
SKILL.md completely.The canonical entrypoints are:
${CODEX_HOME:-$HOME/.codex}/skills/shellscript-coder/SKILL.md${CODEX_HOME:-$HOME/.codex}/skills/ts-coder/SKILL.md${CODEX_HOME:-$HOME/.codex}/skills/python-coder/SKILL.md${CODEX_HOME:-$HOME/.codex}/skills/rust-coder/SKILL.mdDo not substitute a generic coding workflow or launch a nested Codex process. The selected language skill executes directly in the current session.
After completing TypeScript or Python implementation, run $code-simplifier, when it is installed, on the changed production code before final verification.
Use every language skill required by the requested output. Keep one shared task plan and one cross-language contract.
Do not force a mixed task through one specialist and do not launch competing implementations of the same contract.
The language skills are optional. If a selected language skill is not installed, follow the repository's own conventions and say which skill was missing; if an installed skill names a reference that is missing, search its installed roots, read it, and resume. Continue independent repository inspection meanwhile. Ask only for access or an artifact that investigation proves only the owner can supply; do not park the task or emulate unread instructions.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Answer how long agent work will take, how much longer active work needs, or what clock time applies. Estimate full AI-agent wall time, measure active progress first, and get owner-facing times from `sno report-time`. Never estimate human-developer time.
The English summary is being prepared. Showing the original description.
Prove that a reported run caused its intended real effect. Walk the executor path from entry to effect, capture one observable per hop, and report a result a no-op could not produce.
The English summary is being prepared. Showing the original description.
Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.
The English summary is being prepared. Showing the original description.
Report how many problems the two brains found: mutual review (the other model checks the work, from the peer-review records) and self-check (an agent finds its own error in its own conversation, judged by that agent's own model), side by side. Use when the owner asks whether the second agent or the reviews are worth it, or wants the week's review results.
The English summary is being prepared. Showing the original description.
Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter.
The English summary is being prepared. Showing the original description.
Route production coding tasks from Claude Code to the user-level Codex Shell, TypeScript, Python, or Rust workflow through a direct `codex exec` run. Use for "codex-coder", "ask Codex to write code", "generate with Codex", language migrations, or mixed Shell/TypeScript/Python/Rust implementation.
The English summary is being prepared. Showing the original description.