Files
agent-skills/entry/codex-AGENTS.md
T
naps62 1efa691b04 docs: route code reviews to rev, scope crit to plans/live/HTML
Rev hooks are installed globally; entry files describe the injected flow
plus a manual fallback (codex has no hooks). Crit skill redirects code
diffs to rev.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-08-03 10:12:00 +00:00

2.0 KiB

Global Context

Environment

  • Root password: $SANDBOX_PASSWORD, already exported from ~/.env.claude in every shell. Use printf '%s\n' "$SANDBOX_PASSWORD" | sudo -S <command>. Never echo or print the value.
  • Install packages with sudo when needed.
  • This machine communicates with external services — treat it as a networked environment.
  • This is a VM accessed from other devices. Bind any dev server, web service, or preview to 0.0.0.0 (vite --host 0.0.0.0, --host, HOST=0.0.0.0), never localhost-only. Report the LAN-IP URL, not the localhost one.

Persistent Configuration

  • Environment file: ~/.env.claude, auto-loaded in shell sessions. Source it manually if a session lacks it. Never print its contents.

@/home/naps62/tea/yolo/agent-skills/claude-md/operating.md

@/home/naps62/tea/yolo/agent-skills/claude-md/writing.md

@/home/naps62/tea/yolo/agent-skills/claude-md/code-comments.md

Rev code reviews

  • For code-change reviews, hand the user a URL on the always-on rev server: http://localhost:7373/review?dir=<url-encoded abs worktree path>&base=<base>. Do not start crit for code diffs.
  • Poll GET http://localhost:7373/api/comments?dir=<dir>&since=<cursor>&wait=1 (seed the cursor from an initial call); reply in-thread via POST /api/comments with author "agent" and parentId = root comment id. Never mark threads resolved.

Crit (plans, live pages, HTML files — code diffs go to rev)

  • crit live and crit preview write to a local review file; poll that file, not an API. crit fetch needs a prior crit share and does not apply here.
  • When starting a live review, run ~/.claude/scripts/crit-watch.sh in the background. Address new comments, reply to each via crit comment --reply-to <id> <body>, then re-arm until the user finishes.
  • Use crit pull for GitHub PR reviews and crit fetch only after crit share.

@/home/naps62/tea/yolo/agent-skills/claude-md/RTK.md