yolo/agent-skills
3
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

docs: route code reviews to rev, scope crit to plans/live/HTML

Browse Source 
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>
This commit is contained in:
naps62
2026-08-03 10:12:00 +00:00
parent cb525048a4
commit 1efa691b04
3 changed files with 29 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
entry/CLAUDE.md
+15 -1
View File
@@ -18,7 +18,21 @@
@~/.claude/operating.md
## Crit reviews
## Rev code reviews
- Code-change reviews use the always-on rev server on `:7373`. A review is
just a URL — never start crit or any per-review server for code diffs.
- Global hooks do the plumbing: SessionStart injects the review URL and full
instructions in any rev-known repo, and a Stop hook prompts to (re)arm the
comment watcher (`~/tea/yolo/rev/scripts/rev-watch.sh <dir>`, background).
Follow the injected instructions; there is nothing to set up.
- Fallback if no instructions were injected: URL is
`http://<host>:7373/review?dir=<url-encoded worktree>&base=<base>`;
long-poll `GET /api/comments?dir=&since=&wait=1`, reply in-thread via
`POST /api/comments` with author `"agent"` + `parentId`, never mark
threads resolved.
## Crit reviews (plans, live pages, HTML files — code diffs go to rev)
- **`crit live` / `crit preview` write comments to a local review FILE, not an API** — there is NO notification and `crit fetch` does NOT apply (it needs a prior `crit share`). `/api/comments` on the daemon is the WRONG place (stays `[]`). If I launched the crit server myself, I must poll the review file myself.
- **Whenever I start a `crit live`/`crit preview` review for the user, immediately arm the watcher so they don't have to babysit it:**
`~/.claude/scripts/crit-watch.sh` — run it via the Bash tool with `run_in_background: true`. It auto-finds the active live/preview review file (`~/.crit/reviews/<id>/review.json`), baselines existing comment IDs, and re-invokes me with any NEW comments once they settle. When it fires: read the comments, address them, **reply to each via `crit comment --reply-to <id> <body>`**, then re-arm the watcher. Keep doing this until the user says they're done.