AI Code Change Review Router

How to use AI Code Change Review Router

Before accepting generated code, identify the changed files and who must review them. This workbench checks a documented text-diff subset and creates a handoff without applying or running the patch.

1. Paste a plain text unified diff with a/path and b/path headers.
2. Enter exact file or directory prefixes and the responsible reviewers.
3. Review the routed files and attach actual tests in your own repository before applying the change.

Good to know

• At most500 diff lines and 100 files. Supports text hunks, plain no-space paths and /dev/null new/deleted files. Refuses renames/copies, binary patches, quoted paths, timestamps, malformed/overlapping hunks and traversal. No patch is applied.
• Each field is limited to8,000 characters and each CSV to100 data records. Use the exact displayed header; quoted commas, doubled quotes and quoted newlines are supported. IDs and short task descriptions are limited to 200 characters. Numbers use nonnegative ordinary decimal notation with at most 9 fractional places, magnitude at most 999,999,999; no scientific notation. Whole-count limits can be stricter. Results above 1 quadrillion or nonzero below 0.000000000001 are refused.
• Independent deterministic ToolJovia workflow. It does not call an AI model, contact a vendor, fetch sources, send messages, save input or execute code. Editable outputs and downloads contain your data; review before sharing. A prepared plan does not verify customers, revenue or a vendor’s internal workflow.