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

fix: rev fallback asks for multi-line markdown reply bodies

Browse Source 
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
naps62
2026-08-11 20:15:40 +00:00
parent 19bd110188
commit 984616f5c4
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
entry/CLAUDE.md
+3 -2
View File
@@ -30,8 +30,9 @@
`https://rev.n62.casa/review?dir=<url-encoded worktree>&base=<base>`, while `https://rev.n62.casa/review?dir=<url-encoded worktree>&base=<base>`, while
the API to call is `http://localhost:7373`; the API to call is `http://localhost:7373`;
long-poll `GET /api/comments?dir=&since=&wait=1`, reply in-thread via long-poll `GET /api/comments?dir=&since=&wait=1`, reply in-thread via
`POST /api/comments` with author `"agent"` + `parentId`, never mark `POST /api/comments` with author `"agent"` + `parentId` and a real
threads resolved. multi-line markdown body (pipe a heredoc through `jq -Rs`, never a
body inlined on one line), never mark threads resolved.
## Crit reviews (plans, live pages, HTML files — code diffs go to rev) ## 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. - **`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.
entry/codex-AGENTS.md
+1 -1
View File
@@ -23,7 +23,7 @@
## Rev code reviews ## 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. - 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. - 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"`, `parentId` = root comment id, and a real multi-line markdown body (pipe a heredoc through `jq -Rs`, never a body inlined on one line). Never mark threads resolved.
## Crit (plans, live pages, HTML files — code diffs go to rev) ## Crit (plans, live pages, HTML files — code diffs go to rev)