Code Review

Dojo has built-in code review powered by stacks. No need for external tools like GitHub PRs — review happens right in the CLI.

The review flow

1. Author submits a stack

dojo stack submit --title "Refactor database layer"

2. Reviewer views pending stacks

dojo review list

3. Reviewer examines the changes

# Full diff
dojo review diff --number 42

# Only changes since last review
dojo review diff --number 42 --delta

4. Reviewer provides feedback

# Approve
dojo review approve --number 42

# Request changes with reason
dojo review reject --number 42 --message "Missing error handling in auth middleware"

# Leave inline comments
dojo review comment --number 42 --message "Consider using a Map here instead"

5. Author addresses feedback

# Edit the relevant commit
dojo edit <commit-id>

# Make fixes...
dojo commit -m "Address review feedback"

# Push updates
dojo sync push

6. Reviewer checks the delta

# See only what changed since last review
dojo review diff --number 42 --delta

Review statuses

Status	Meaning
draft	Not yet submitted for review
review	Awaiting review
approved	Approved by reviewer(s)
merged	Merged into main

Best practices

• Keep stacks focused — one logical change per stack
• Write clear titles — summarize what the stack does
• Use delta reviews — after updates, only review what changed
• Comment constructively — explain the “why” not just the “what”