How this skill is triggered — by the user, by Claude, or both
Slash command
/humanize:codex-worker [--worker-model MODEL:EFFORT] [--worker-timeout SECONDS] [--workdir PATH] [task or instructions][--worker-model MODEL:EFFORT] [--worker-timeout SECONDS] [--workdir PATH] [task or instructions]This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run Codex CLI as the **implementation worker** for `coding` tasks.
Run Codex CLI as the implementation worker for coding tasks.
Do not pass free-form user text to the shell unquoted. The task may contain spaces or shell metacharacters such as (, ), ;, #, *, or [.
If the user only supplied a task or instructions, execute:
"${CLAUDE_PLUGIN_ROOT}/scripts/codex-worker.sh" "$ARGUMENTS"
If the user supplied flags such as --worker-model, --worker-timeout, or --workdir, reconstruct the command so those flags remain separate shell arguments and the remaining free-form task is passed as one quoted final argument.
Example:
"${CLAUDE_PLUGIN_ROOT}/scripts/codex-worker.sh" --worker-model gpt-5.4:xhigh --workdir /repo/worktree "Implement the pending coding task and run relevant checks"
Never run this unsafe form:
"${CLAUDE_PLUGIN_ROOT}/scripts/codex-worker.sh" $ARGUMENTS
because the shell will re-parse the task text and can fail before codex-worker.sh starts.
| Exit Code | Meaning |
|---|---|
| 0 | Success - worker response is in stdout |
| 1 | Validation error (missing codex, empty task, invalid flags, empty response) |
| 124 | Timeout - suggest using --worker-timeout with a larger value |
| Other | Codex process error - report the exit code and any stderr output |
gpt-5.4:xhigh.humanize/skill/<timestamp>/output.md for referencenpx claudepluginhub zenuszhang/humanizeGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.