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ê.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Run Codex CLI, Claude Code, OpenCode, or Pi Coding Agent via background process for programmatic control.
Coding Agent (background-first)
Use bash background mode for non-interactive coding work. For interactive coding sessions, use the tmux skill (always, except very simple one-shot prompts).
The Pattern: workdir + background
# Create temp space for chats/scratch work
SCRATCH=$(mktemp -d)
# Start agent in target directory ("little box" - only sees relevant files)
bash workdir:$SCRATCH background:truecommand:"<agent command>"# Or for project work:
bash workdir:~/project/folder background:truecommand:"<agent command>"# Returns sessionId for tracking# Monitor progress
process action:log sessionId:XXX
# Check if done
process action:poll sessionId:XXX
# Send input (if agent asks a question)
process action:write sessionId:XXX data:"y"# Kill if needed
process action:kill sessionId:XXX
Why workdir matters: Agent wakes up in a focused directory, doesn't wander off reading unrelated files (like your soul.md 😅).
Codex CLI
Model:gpt-5.2-codex is the default (set in ~/.codex/config.toml)
Building/Creating (use --full-auto or --yolo)
# --full-auto: sandboxed but auto-approves in workspace
bash workdir:~/project background:truecommand:"codex exec --full-auto \"Build a snake game with dark theme\""# --yolo: NO sandbox, NO approvals (fastest, most dangerous)
bash workdir:~/project background:truecommand:"codex --yolo \"Build a snake game with dark theme\""# Note: --yolo is a shortcut for --dangerously-bypass-approvals-and-sandbox
Reviewing PRs (vanilla, no flags)
⚠️ CRITICAL: Never review PRs in Clawdbot's own project folder!
Either use the project where the PR is submitted (if it's NOT ~/Projects/clawdbot)
Or clone to a temp folder first
# Option 1: Review in the actual project (if NOT clawdbot)
bash workdir:~/Projects/some-other-repo background:truecommand:"codex review --base main"# Option 2: Clone to temp folder for safe review (REQUIRED for clawdbot PRs!)
REVIEW_DIR=$(mktemp -d)
git clone https://github.com/clawdbot/clawdbot.git $REVIEW_DIRcd$REVIEW_DIR && gh pr checkout 130
bash workdir:$REVIEW_DIR background:truecommand:"codex review --base origin/main"# Clean up after: rm -rf $REVIEW_DIR# Option 3: Use git worktree (keeps main intact)
git worktree add /tmp/pr-130-review pr-130-branch
bash workdir:/tmp/pr-130-review background:truecommand:"codex review --base main"
Why? Checking out branches in the running Clawdbot repo can break the live instance!
Batch PR Reviews (parallel army!)
# Fetch all PR refs first
git fetch origin '+refs/pull/*/head:refs/remotes/origin/pr/*'# Deploy the army - one Codex per PR!
bash workdir:~/project background:truecommand:"codex exec \"Review PR #86. git diff origin/main...origin/pr/86\""
bash workdir:~/project background:truecommand:"codex exec \"Review PR #87. git diff origin/main...origin/pr/87\""
bash workdir:~/project background:truecommand:"codex exec \"Review PR #95. git diff origin/main...origin/pr/95\""# ... repeat for all PRs# Monitor all
process action:list
# Get results and post to GitHub
process action:log sessionId:XXX
gh pr comment <PR#> --body "<review content>"
Use the tmux skill for interactive coding sessions (always, except very simple one-shot prompts). Prefer bash background mode for non-interactive runs.
Parallel Issue Fixing with git worktrees + tmux
For fixing multiple issues in parallel, use git worktrees (isolated branches) + tmux sessions:
Why worktrees? Each Codex works in isolated branch, no conflicts. Can run 5+ parallel fixes!
Why tmux over bash background? Codex is interactive — needs TTY for proper output. tmux provides persistent sessions with full history capture.
⚠️ Rules
Respect tool choice — if user asks for Codex, use Codex. NEVER offer to build it yourself!
Be patient — don't kill sessions because they're "slow"
Monitor with process:log — check progress without interfering
--full-auto for building — auto-approves changes
vanilla for reviewing — no special flags needed
Parallel is OK — run many Codex processes at once for batch work
NEVER start Codex in ~/clawd/ — it'll read your soul docs and get weird ideas about the org chart! Use the target project dir or /tmp for blank slate chats
NEVER checkout branches in ~/Projects/clawdbot/ — that's the LIVE Clawdbot instance! Clone to /tmp or use git worktree for PR reviews
PR Template (The Razor Standard)
When submitting PRs to external repos, use this format for quality & maintainer-friendliness:
## Original Prompt
[Exact request/problem statement]
## What this does
[High-level description]
**Features:**- [Key feature 1]
- [Key feature 2]
**Example usage:**```bash
# Example
command example
```## Feature intent (maintainer-friendly)
[Why useful, how it fits, workflows it enables]
## Prompt history (timestamped)- YYYY-MM-DD HH:MM UTC: [Step 1]
- YYYY-MM-DD HH:MM UTC: [Step 2]
## How I tested**Manual verification:**1. [Test step] - Output: `[result]`2. [Test step] - Result: [result]
**Files tested:**- [Detail]
- [Edge cases]
## Session logs (implementation)- [What was researched]
- [What was discovered]
- [Time spent]
## Implementation details**New files:**-`path/file.ts` - [description]
**Modified files:**-`path/file.ts` - [change]
**Technical notes:**- [Detail 1]
- [Detail 2]
---
*Submitted by Razor 🥷 - Mariano's AI agent*
