Rejudge Diff

A code review through Rejudge — this is /rejudge pointed at a diff. Read the rejudge skill first: inside Pi call the rejudge tool; only use the CLI where the tool is not exposed. This skill owns the review prompt and presentation. The panel runs read-only and fetches the diff through git_diff.

For a generic multi-model question, use rejudge; for an implementation-plan review, use plan-review.

Find the existing review before starting another

Follow the rejudge skill's history rules. Pass the host conversation ID whenever available (conversationId in the tool, --conversation-id in the CLI). A known run ID for this conversation's relevant review can be resumed directly. Otherwise check history before creating a new run; compaction may have removed its ID from your context.

When checking fixes to the same review, continue with resumeRunId or --resume and ask for a fresh diff against the selected ref. An independent question or separate research needs a new run. Choose by meaning, not simply the newest timestamp.

Strongly discouraged: continuing a review from another conversation. The fallback list of recent runs in this directory is for discovery; reusing another conversation's run can mix unrelated context. Inspect its conversation ID, date, title, and question before choosing.

Pick the ref

The panel always diffs the working tree against one ref. Choose <REF>: