Menu
Control herdr from Codex. Use when the user says "use Herder" or asks to inspect, focus, prompt, spawn, or manage herdr workspaces, tabs, panes, or agents from a Codex session, without deciding whether they are inside or outside herdr.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Run two heterogeneous fresh-context Herdr reviewers against both code quality and a governing plan, then synthesize evidence-backed feedback. Use when the user asks for a dual or adversarial review, code-versus-plan verification, or independent Claude and Pi reviewers before deciding whether a PR needs changes.
Use when the user explicitly asks Codex Desktop or another shell outside Herdr to create, inspect, prompt, follow up with, or monitor Herdr agent tabs, or when the `codex-herdr` router skill hands off external control.
Fan out a user-provided task list into one reviewed PR per task through Herdr, then shepherd the PR fleet through CI and review without merging. Use when the user asks to fan out PRs, parallelize backlog items into separate PRs, or autonomously drive multiple agent-owned PRs to green.
Inspect and import content into my self-hosted AutoCaliWeb library. Use for catalog status, search, recent imports, shelves, metadata, or importing an ebook, comic, PDF, or audiobook.
Correct-by-construction TypeScript standards. Use for TypeScript engineering or when another skill needs the user's coding standards.
Design Effect services. Use when designing a new Effect service module or auditing an existing codebase for service, Layer, and composition improvements.
| name | codex-herdr |
| description | Control herdr from Codex. Use when the user says "use Herder" or asks to inspect, focus, prompt, spawn, or manage herdr workspaces, tabs, panes, or agents from a Codex session, without deciding whether they are inside or outside herdr. |
Router for controlling herdr from Codex. "Herder" and "herder" in a request mean herdr; the CLI binary is always herdr. Pick the workflow from the environment; the user never has to.
echo "${HERDR_ENV:-unset}".HERDR_ENV=1, you are inside a herdr-managed pane. Read and follow the sibling herdr skill (../herdr/SKILL.md) — the native workflow.herdr-dispatch requires. Read and follow the sibling herdr-dispatch skill (../herdr-dispatch/SKILL.md). Verify connectivity first with herdr workspace list; if it fails, herdr is not running — report that and stop.The herdr skill's HERDR_ENV gate is intentional: it stops an outside shell from acting as if it owned the focused pane. Never set or fake HERDR_ENV to reach the native path, and never treat the focused pane as yours from outside. External control always goes through herdr-dispatch.