Capture feedback and review notes alongside changes.
Review needs a place to capture feedback. In IOModel today, review notes live where the change does: in commit messages, in the diff you review, and in the specs that describe intent.
Where feedback lives
| Channel | Use for |
|---|---|
| Commit messages | Why a change was made |
| Diff review | What changed, line by line |
| Spec prose | Decisions, rationale, and open questions |
| Branch description | Scope and status of in-progress work |
A lightweight review-notes practice
Record intent in commits
Write commit messages that explain the why, not just the what.
Capture open questions in specs
Note unresolved decisions directly in the relevant spec page.
Review against the diff
Walk the branch diff and discuss specific changes with your team.
Keep feedback close to the change
Anchor feedback to commits, the visual diff, and spec prose so it stays next to the work it refers to and survives long after a conversation ends.
Treat the spec itself as the durable record. Decisions written into the spec outlive any comment thread and stay visible to future readers.
Last updated on