Anti-Vibe

Push a FLOW-ORDERED code review to Anti-Vibe: the human walks the change in runtime execution order (like a sequence diagram), not file-by-file. Send ONLY the traversal STRUCTURE — never the diff text. Anti-Vibe resolves each hunk by running `git diff` in the repo and matching your locators. Order `flow` stops top→bottom in call order (entry → handler → service → effect); put models/schemas/contracts/types in `foundation` and list them bottom→up. Each stop maps to a FILE — the reviewer steps through all of that file's hunks one at a time. `locator` is an OPTIONAL hint (exact `hunkHeader` "@@ -a,b +c,d @@ ..." or `lineRange`) that just sets the match-confidence badge. Give each stop a one-line summary. For unchanged connective steps (a dispatcher/existing handler the flow passes through), add a stop with `context: true` and no locator so the sequence reads continuously. When a stop's file has several hunks, add `hunkFlow` to order them for reading in execution order (behavior change before plumbing) with a one-line note per hunk.

Send markdown to the Anti-Vibe reader so a human can review it without fatigue, moving heading-by-heading and optionally speed-reading each section. Provide your output as well-structured Markdown — use `#`/`##`/`###` headings to break it into sections (Anti-Vibe navigates by heading), plus normal Markdown for lists, tables, code blocks and emphasis. Pass the full content in `markdown`. For CODE REVIEW / diff content: one `###` heading per file, and NEVER paste a whole file or diff as a single fenced block — each fenced block is one atomic step in the reader, so an oversized block becomes an unreviewable wall. Split code into small fenced blocks (one function or one logical hunk, ~15 lines each) and precede each block with one line of prose saying WHY that piece exists. This applies doubly to NEW files: present them one function/section at a time, never verbatim top-to-bottom. Opens the Anti-Vibe tab on first use and live-updates it on later calls.

Send an agent response to the Anti-Vibe reader OPTIMIZED for RSVP speed-reading, where one word is flashed at a time. Because raw agent output reads badly word-by-word, YOU must rewrite the content before passing it in `markdown`: (1) Rephrase into flowing, natural prose — full sentences, minimal symbols, no bullet fragments or telegraphic notes; write it as if it were read aloud. (2) Replace every code block with a short PROSE SUMMARY of what the code does (e.g. "A function that validates the token expiry using a strict less-than check."). Do not paste raw code into the prose — summarize it. (3) Keep `#`/`##` headings as the section spine. (4) When a TABLE or other structured element is essential to keep verbatim, include it as a normal Markdown table/code block — Anti-Vibe renders these as atomic blocks and AUTO-PAUSES the RSVP stream on them so the reader stops and studies them, then resumes. Use this tool for content a human will speed-read; use `review_markdown` to preserve the original code and structure verbatim.