Code review change requests: six recorded examples
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
Read the current reviewer's comment to separate a concrete modification request from approval, explanation or a declined quoted suggestion. Preserve ambiguous attribution before acting on the comment.
This decision belongs before a patch-writing queue. It separates comments that ask for work from comments that acknowledge, explain or approve the current implementation.
Attribution matters. A reviewer can quote a previous change request to disagree with it. Read the surrounding stance instead of treating every imperative inside quotation marks as an instruction.
The jevable package demonstrates filtering review comments with a Jev test. This original example makes unresolved intent explicit and stops at a label; it does not connect to a repository or post a review reply.
This is an independently authored text demonstration inspired by the linked X discussion. Its rules and synthetic inputs are ours. It does not reproduce the author’s application, verify reported outcomes, or perform an external action.

Use the sample to understand the rule, then test your own input for code review change requests.

Read the current reviewer's comment to separate a concrete modification request from approval, explanation or a declined quoted suggestion.

Open the decision rules and keep the intended distinction between Change requested, No change requested, Review. Edit the choices only when testing your own rule.

Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

Review Review before using a result. The label is a decision about the supplied information, not an executed action.
| Original input | Observed label | Leading probability |
|---|---|---|
| Direct rename | Change requested | 100% |
| Polite request | Change requested | 100% |
| Approval | No change requested | 100% |
| Quoted request rejected | No change requested | 93.0% |
| Explanation only | No change requested | 97.0% |
| Missing comment context | Review | 96.0% |
These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified
The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.
The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json
# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.The input contract and these limits define what the result means.
No. A question can ask for an explanation or ask someone to modify code. The surrounding wording and reviewer stance distinguish those uses.
The output only says whether a change was requested. A separate step needs the code and review context to understand and evaluate the proposed repair.
It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.
No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.
Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.