Files

T

Miguel Palhas d6265b0fbe

ci / nix (push) Successful in 13s

Details

ci / lint (push) Successful in 29s

Details

rev is a nix package now and puts rev-watch on PATH. The old path pointed into
a working checkout, which is dev-only from here on.

2026-08-25 10:01:40 +01:00

Global Context

@~/.claude/machine.md

Browser automation

Use the agent-browser CLI (headless, via Bash) for anything browser-shaped: checking pages, dev servers, screenshots, form flows, console/eval. agent-browser --help lists commands; snapshot gives an accessibility tree with refs for AI use.
The claude-in-chrome extension is disabled by default. Only reach for it if the task genuinely needs my real logged-in browser session or open tabs — and if its tools aren't available, ask me to enable it rather than working around it.

@~/.claude/writing.md

@~/.claude/operating.md

@~/.claude/intercomms.md

Rev is for showing me changes you wrote. Reviewing a PR someone else authored is a different job: those findings go on the PR itself through the forge API, never into rev. A review parked in rev under a worktree path disappears with the worktree, and the PR is left looking unreviewed.
For code-change reviews, hand me a URL on the always-on rev server: https://rev.n62.casa/review?dir=<url-encoded worktree>&base=<base>. Global hooks inject the URL and full instructions automatically in any rev-known repo — follow those.
Fallback: API is http://localhost:7373; long-poll GET /api/comments?dir=&since=&wait=1, reply via POST /api/comments with author "agent" + parentId and a real multi-line markdown body (pipe a heredoc through jq -Rs, never inlined on one line). Never mark threads resolved. Arm/re-arm the watcher (rev-watch <dir>) silently — never announce its state in chat.

@~/.claude/RTK.md