Flowchart

Code review process flowchart template

A code review flowchart: open a pull request, automated checks, assign reviewers, comments, changes, approval and merge, with loops for failed checks and requested changes. Adapt it to your team's conventions, then export PNG, SVG, Word or PowerPoint free.

No

Yes

Yes

No

Yes

No

Developer finishes and self-tests

Open a pull request

Automated checks build tests lint

Checks pass

Fix the issues

Assign a reviewer

Reviewer reads the change

Changes requested

Developer updates and replies

Approve

Second reviewer required

Merge to main

Delete branch and link the issue

Previewed in the “Light” theme; you can switch themes in the editor

When to use it

Use it when a team wants one way of doing code review, or to show a new member what happens after they open a pull request. Automated checks come before people, and comments loop between updating and re-reading until approval.

Make it yours

  • Keep the second reviewer decision for core modules; small teams can delete it.
  • Put the expected turnaround in a node, such as "First response within one business day".
  • If you require a merge method, say so in the last step, such as squash merge.

Mermaid code

code-review-flowchart.mmd
flowchart TD
    A[Developer finishes and self-tests] --> B[Open a pull request]
    B --> C[Automated checks build tests lint]
    C --> D{Checks pass}
    D -->|No| E[Fix the issues] --> B
    D -->|Yes| F[Assign a reviewer]
    F --> G[Reviewer reads the change]
    G --> H{Changes requested}
    H -->|Yes| I[Developer updates and replies]
    I --> G
    H -->|No| J[Approve]
    J --> K{Second reviewer required}
    K -->|Yes| F
    K -->|No| L[Merge to main]
    L --> M[Delete branch and link the issue]

Ask an AI for one with this structure

Send the prompt below to ChatGPT or Claude, then paste the whole reply into the editor; the code inside is detected automatically.

prompt.txt
Draw a code review flowchart with Mermaid flowchart TD syntax. The developer finishes and self-tests, opens a pull request, and automated checks run; if they fail, fix the issues and resubmit. If they pass, assign a reviewer who reads the change. If changes are requested, the developer updates and replies and the reviewer reads again. If not, approve. If a second reviewer is required, assign again; otherwise merge to main, delete the branch and link the issue. Use diamonds for decisions and no parentheses in node text. Output only the mermaid code block.

FAQ

How do I show blocking versus optional comments?

Split the decision into two exits, "Must fix" and "Suggestion", and send suggestions straight to approval.

Can it go into our engineering handbook?

Yes. SVG is the sharpest in documents, or use a share link so everyone opens the current version.

Can I show how long reviews take?

Add the target to the reviewer node with a line break. Actual durations belong in your metrics dashboard, not on the chart.

More in this category

All templates

Updated 2026-11-11