skills/humanize/SKILL.md
Iterative development with AI review. Provides RLCR (Ralph-Loop with Codex Review) for implementation planning and code review loops, plus PR review automation with bot monitoring.
npx skillsauth add cupnfish/humanize-rs humanizeInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Humanize creates a feedback loop where AI implements your plan while another AI independently reviews the work, ensuring quality through continuous refinement.
All command examples below use the humanize CLI available on PATH:
humanize
Iteration over Perfection: Instead of expecting perfect output in one shot, Humanize leverages an iterative feedback loop where:
The RLCR (Ralph-Loop with Codex Review) loop has two phases:
Phase 1: Implementation
Phase 2: Code Review
codex review --base <branch> checks code quality[P0-9] severity markershumanize gate rlcr to enforce hook-equivalent transitions and blockingAutomates handling of GitHub PR reviews from remote bots:
--claude and/or --codex)@botTransforms a rough draft document into a structured implementation plan with:
When running inside Claude Code, prefer the humanize-gen-plan flow/skill behavior:
humanize config merged --json --with-meta to read merged plan-generation defaultshumanize gen-plan --prepare-only for deterministic validation and scaffold preparationhumanize ask-codex for first-pass and convergence reviewsThe full humanize gen-plan command remains available for standalone terminal workflows.
# With a plan file
humanize setup rlcr path/to/plan.md
# Or without plan (review-only mode)
humanize setup rlcr --skip-impl
# For each round, run the RLCR gate (required)
humanize gate rlcr
Common Options:
--max or --max-iterations N - Maximum iterations before auto-stop (default: 42)--codex-model MODEL:EFFORT - Codex model and reasoning effort for codex exec (default: gpt-5.4:xhigh)codex review uses gpt-5.4:high--codex-timeout SECONDS - Timeout for each Codex review (default: 5400)--base-branch BRANCH - Base branch for code review (auto-detects if not specified)--full-review-round N - Interval for full alignment checks (default: 5)--skip-impl - Skip implementation phase, go directly to code review--track-plan-file - Enforce plan-file immutability when tracked in git--push-every-round - Require git push after each round--claude-answer-codex - Let Claude answer Codex Open Questions directly (default is AskUserQuestion behavior)--agent-teams - Enable Agent Teams modehumanize cancel rlcr
# or force cancel during finalize phase
humanize cancel rlcr --force
# Monitor claude[bot] reviews
humanize setup pr --claude
# Monitor chatgpt-codex-connector[bot] reviews
humanize setup pr --codex
# Monitor both
humanize setup pr --claude --codex
Common Options:
--max or --max-iterations N - Maximum iterations (default: 42)--codex-model MODEL:EFFORT - Codex model for validation (default: gpt-5.4:medium)--codex-timeout SECONDS - Timeout for Codex validation (default: 900)humanize cancel pr
humanize gen-plan --prepare-only --input path/to/draft.md --output path/to/plan.md
Then continue with host-driven Codex consultation, convergence, clarification, and plan authoring.
humanize ask-codex [--model MODEL] [--effort EFFORT] [--timeout SECONDS] "your question"
The RLCR loop uses a Goal Tracker to prevent goal drift:
humanize gate rlcr instead of manual phase controlhumanize - Humanize CLIcodex - OpenAI Codex CLI (for review)gh - GitHub CLI (for PR loop)development
Start RLCR (Ralph-Loop with Codex Review) with hook-equivalent enforcement from skill mode by reusing the existing native `humanize gate rlcr` logic.
tools
Generate a structured implementation plan from a draft document. The host orchestrates repository analysis, Codex planning rounds, convergence, user clarification, and final authoring. The CLI provides deterministic helper commands for config lookup, validation, scaffold preparation, and one-shot Codex consultation.
development
Consult Codex as an independent expert. Sends a question or task to `humanize ask-codex` and returns the response.
tools
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.