Human review of the diff

Shows the diff to a person before the pull request exists. Their notes go back to the agent to address, or they approve it as it stands.

Template	human-code-review
Works on	A git repository, cloned into an isolated Docker sandbox
Where a person acts	Review the implementation diff — a person reviews and annotates, waiting up to 8h Apply the reviewer notes before opening the PR? — a person chooses a path, waiting up to 30m

The workflow

Drawn from the template spec at build time. Bookkeeping nodes that only record status are left out; amber nodes are where a person acts.

flowchart TD
  n_validate["Validate"]
  n_implement["Implement"]
  n_runLint["Run lint"]
  n_runTypecheck["Run typecheck"]
  n_humanReview>"Review the implementation diff<br/><small>person: review</small>"]
  n_applyFeedbackDecision>"Apply the reviewer notes before opening the PR?<br/><small>person: decision</small>"]
  n_openPR["Open PR"]
  n_addressFeedback["Address feedback"]
  n_done(["Done"])
  n_validate --> n_implement
  n_implement --> n_runLint
  n_runLint --> n_runTypecheck
  n_runTypecheck --> n_humanReview
  n_humanReview -->|"submitted"| n_applyFeedbackDecision
  n_humanReview -->|"timed out"| n_openPR
  n_applyFeedbackDecision -->|"timed out"| n_openPR
  n_applyFeedbackDecision -->|"Yes — apply the notes"| n_addressFeedback
  n_applyFeedbackDecision -->|"No — looks good, open PR"| n_openPR
  n_openPR --> n_done
  n_addressFeedback --> n_openPR
  class n_humanReview,n_applyFeedbackDecision gate

Maturity: built from the flagship steps

Ships as a built-in template and reuses the engineering steps the flagship flow runs. This particular arrangement of them is not separately exercised end to end against a real repository. See product overview §8.

Use it

Every built-in template is seeded into the workflow library and can be cloned, edited on the visual canvas, and versioned — see architecture for the node types. The spec lives in packages/shared/src/workflow/templates/humanCodeReview.ts.