메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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"
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.
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.
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.
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.
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.
| 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. |
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.
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.
Include:
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.