# How to walk a team through your pull request

> A code walkthrough is ten minutes, in this order: the problem, the change in reading order, what you are unsure about, how it was tested, and how to undo it.

Source: https://hintvo.com/blog/walk-a-team-through-your-pull-request | Last updated: November 20, 2026 | Reviewed: 2026-11-20

A walkthrough goes wrong when the author scrolls through the files in the order the tool shows them. The people watching need a different order: the problem first, then the change in the order a reader would follow it, then what you are unsure about. Ten minutes is enough.

## Start with the problem

One or two sentences on what was wrong or missing, in terms of what a user or another engineer experienced. Reviewers who do not know why the change exists will review the style, because that is all they can judge.

## Show the change in reading order

1. **Data first.** New tables, columns or types. Everything else depends on them.
2. **Then the main path.** The one function or handler where the new behavior lives.
3. **Then the edges.** Error handling, permissions, the old behavior you kept.
4. **Tests last.** They are the summary of what you claim the change does.

Skip the renames and the formatting. Say that they exist and that they change nothing.

## Say what you are unsure about

This is the most useful minute. "I am not sure the retry belongs in the consumer and not in the charge function" tells reviewers where to spend their attention. A change presented as finished gets a nod. A change presented with its open question gets a real review.

## How it was tested, and how to undo it

- What you ran, and what you did by hand.
- What you did not test, said plainly.
- How to turn it off or roll it back if it misbehaves in production.

## Ask specific questions

"Any thoughts?" gets silence. "Is two seconds a sensible timeout for this call?" gets an answer. Bring two or three questions like that and ask them by name if the room is quiet.

## After the walkthrough

Write the decisions into the pull request itself, not into a chat that scrolls away. The next person to read this code will look there first.

> **Where Hintvo fits:** when a walkthrough ends, Hintvo writes the notes: decisions, open questions and action items with owners and the files they touch. During the call, questions about how the current code behaves get an answer with its file and line. Meeting notes need a pack of hours. See [how it works in meetings](https://hintvo.com/meeting-assistant-for-developers).

## Related

- [AI meeting assistant for developers, with answers from your code](https://hintvo.com/meeting-assistant-for-developers.md): How does Hintvo AI help in sprint planning, design reviews and incident calls?
- [Design reviews: ten questions worth asking](https://hintvo.com/blog/design-review-questions-worth-asking.md): What questions should I ask in a design review?
- [Write the decision down: a one-page decision record](https://hintvo.com/blog/write-the-decision-down.md): How do I record a technical decision so the team does not argue about it again?
