DIXI Spec Kit documentation Español · Source on GitHub

/dixi.review

Purpose

Prepare a risk-based human review of a change.

Prepare, for a person, the review of the change against the base in $ARGUMENTS. This review approves nothing.

Generated by scripts/build-command-reference.py from the packaged command text; do not edit by hand.

Invocation

Argument: [base branch or commit, default main]. Angle brackets mark a required value and square brackets an optional one. In the steps, $ARGUMENTS is the text written after the command.

Example

The text after the command is the request; change it to match your project.

When to use it

Steps

  1. Take the base from $ARGUMENTS (default main) and read the diff with git diff <base>...HEAD, without modifying the repository.
  2. Classify risk (low, medium, high) by what it touches: contracts, data, security, permissions, migrations.
  3. Check criterion → change → test: every affected criterion needs a change and a test; every change, a criterion.
  4. List findings with file and line, most severe first. Separate facts from suspicions.
  5. Check that frozen tests did not change in the diff; if they did, that is a blocking finding.
  6. Deliver a checklist for the human reviewer. Approval and merge are theirs.

Files read and written

Paths named by the command text:

Stops and human gates

Closing

Run dixi check before finishing and report: files touched, checks (run, failed, not run), open items and the suggested next command.

Next step

No fixed next operation; /dixi.status suggests one.