Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

dispatch-codex

Estrellas1

Forks0

Actualizado12 de junio de 2026 a las 04:35

Dispatch a peer Codex agent. Use for "$dispatch-codex", "peer Codex agent", "peer agent", "separate Codex agent", "new Codex thread", or when the user asks for another Codex agent working beside this one. This is not a subagent.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

jasonkuhrt

jasonkuhrt/dotfiles

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	dispatch-codex
description	Dispatch a peer Codex agent. Use for "$dispatch-codex", "peer Codex agent", "peer agent", "separate Codex agent", "new Codex thread", or when the user asks for another Codex agent working beside this one. This is not a subagent.

Dispatch Codex

Start a peer Codex agent: a separate Codex thread working beside the current thread. Use this when the user says "peer", "separate Codex agent", or $dispatch-codex.

Hard Distinction

Do not use a subagent or multi-agent helper tool for this skill. A peer Codex agent is a separate Codex thread. It has its own conversation, can work independently, and is not an in-thread helper.

User intent	Correct dispatch
"$dispatch-codex", "spawn a peer Codex agent", "separate Codex agent"	`dispatch-codex`
"$dispatch-codex-sub", "subagent", "in-thread helper"	`dispatch-codex-sub`
"$dispatch-claude", "Claude agent"	`dispatch-claude`

If the user says "peer agent" without a vendor, prefer dispatch-codex in a Codex session.

Procedure

Decide whether the peer should share the current worktree or use an isolated worktree.
- Same worktree: use only when the user explicitly asks for "this worktree" or when shared uncommitted edits are the point.
- New worktree: prefer for broad implementation work that may conflict with the current thread.
Create a separate Codex thread with the current repo/project target. If a Codex thread-creation tool is not already loaded, discover/load that tool first; do not fall back to a subagent.
Give the peer a bounded, self-contained task.
Tell the peer whether other agents are editing the same repo and which files it owns.
Do not wait by default. Continue local critical-path work unless the peer's result is immediately needed.

Prompt Shape

Include:

repo/worktree path
branch or head SHA when relevant
task objective
explicit write scope
verification expectations
reminder not to revert unrelated edits

Example:

Work in <repo path>. Implement <bounded task>. Own <files/modules>. Other agents
may be editing this repo; preserve unrelated changes. Run targeted checks and
report changed files plus unresolved decisions.

Más de este repositorio

mismo repositorio

spelunking

jasonkuhrt/dotfiles

Use when a tool, library, or framework doesn't support what you need and official docs don't cover it — finding solutions off the happy path. Triggers on "how do I make X do Y", "X doesn't support Y", undocumented behavior, bleeding-edge tool limitations, workarounds for missing features, or when the mainstream answer is "you can't do that"

2026-06-161

refactor-review-loop

jasonkuhrt/dotfiles

Iteratively review, refactor, verify, and commit toward less code by sharing primitives and improving functional composition. Use when the user asks for a strict refactor review loop, "get a review strictly for refactoring to less code", "repeat review/fix/commit until empty", or similar wording.

2026-06-121

sync

jasonkuhrt/dotfiles

Use when the user says "sync" or wants to commit, rebase, push, and converge this dotfiles repo. Uses just up as the public converge command.

2026-06-121

gh-ci

jasonkuhrt/dotfiles

Poll, diagnose, and report on a GitHub PR's CI. Use this skill whenever you're about to watch a PR's CI to a terminal state — after pushing commits to a PR, after /git_sync, when the user says "is CI green", "wait for CI", "check the PR's checks", "monitor CI", "did CI pass", "watch the workflow", "fix CI failures", or any phrasing that asks whether a PR is ready to merge based on its checks. ALSO use proactively whenever you push a commit to a branch that has an open PR — never spin up an ad-hoc `gh pr checks --watch` or count-based poll. This skill is the only authority for PR CI status; ignore any older guidance suggesting otherwise.

2026-06-121

gh-close-review-threads

jasonkuhrt/dotfiles

Complete GitHub PR review-comment closeout. Use whenever the user asks to address, fix, handle, clear, close, resolve, respond to, or follow up on PR review comments, review threads, requested changes, bot findings, CodeRabbit, Greptile, or Devin review feedback. Addressing a review thread includes a written thread reply and resolving the thread after the fix or justification is pushed.

2026-06-121

land-complete

jasonkuhrt/dotfiles

Orchestrate land-pr, gh-ci, and land-merged into one end-to-end landing pipeline. Use when the user asks to land complete, land and merge, merge on green, finish a PR end to end, or land without another confirmation loop.

2026-06-121

Dispatch Codex

Start a peer Codex agent: a separate Codex thread working beside the current thread. Use this when the user says "peer", "separate Codex agent", or $dispatch-codex.

Hard Distinction

User intent

Correct dispatch

"$dispatch-codex", "spawn a peer Codex agent", "separate Codex agent"

dispatch-codex

"$dispatch-codex-sub", "subagent", "in-thread helper"

dispatch-codex-sub

"$dispatch-claude", "Claude agent"

dispatch-claude

If the user says "peer agent" without a vendor, prefer dispatch-codex in a Codex session.

Procedure

Decide whether the peer should share the current worktree or use an isolated worktree.

Same worktree: use only when the user explicitly asks for "this worktree" or when shared uncommitted edits are the point.
New worktree: prefer for broad implementation work that may conflict with the current thread.

Create a separate Codex thread with the current repo/project target. If a Codex thread-creation tool is not already loaded, discover/load that tool first; do not fall back to a subagent.

Give the peer a bounded, self-contained task.

Tell the peer whether other agents are editing the same repo and which files it owns.

Do not wait by default. Continue local critical-path work unless the peer's result is immediately needed.

Prompt Shape

Include:

repo/worktree path

branch or head SHA when relevant

task objective

explicit write scope

verification expectations

reminder not to revert unrelated edits

Example:

Work in <repo path>. Implement <bounded task>. Own <files/modules>. Other agents may be editing this repo; preserve unrelated changes. Run targeted checks and report changed files plus unresolved decisions.