DIXI Spec Kit documentation Español · Source on GitHub

/dixi.risk-review

Purpose

Prepare a risk review report of a pull request, branch or diff for a person.

Prepare, for a person, a risk review report of the change in $ARGUMENTS (pull request number, branch or base; by default the current branch against main). This report approves nothing.

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

Invocation

Argument: [pull request number, branch or base, default current branch against 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. Get the diff without modifying anything: git diff <base>...HEAD and git diff --stat <base>...HEAD, or gh pr diff <n> if gh is available and $ARGUMENTS is a pull request number.
  2. Measure the size with dixi pr-size --base <base>. Tests are reported apart; read them first.
  3. Find the spec and the task the change implements (05-features/*/feature-spec.md, 05-features/*/tasks.md, .dixi/traceability.json). If there is none, that is the first finding.
  4. Classify the risk (low, medium, high) by what it touches: contracts, data, security, permissions, migrations, money, external input. If the author declared a lower risk, point it out: risk goes up, never down.
  5. Explain the diff against the spec, criterion by criterion: what changes in observable behavior and which test covers it.
  6. List the edge cases handled and not handled (empty values, limits, nulls, concurrency, time zones, rounding).
  7. List the assumptions the change makes that are not in the spec; each one is a question for the author.
  8. Say what could break outside the changed files: callers, contracts, data, configuration.
  9. Check that frozen tests did not change and that no test was newly skipped; if so, that is a blocking finding.
  10. Deliver the report: risk and why, size, criteria table (criterion, test, status), assumptions, where to look first (file and line, and why), findings by severity, questions for the author and what can be ignored. Put critical findings first. Approval and merge belong to the person.

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.