know what you're approving for real

2 min read Original article ↗

The pull request is excalidraw/excalidraw#8613. The people and chat around it are made up.

Next time a review request lands

You start from what the change is for, not from the top of the file list. By the time you read a line, you know why it's there and what else it touches.

And when you approve, you can tell your colleague why.

Dedicate your focus to what's important

You don't need to read all lines when agents are writing the code.

An agent writes more in an hour than you can read in an afternoon, and most of it is wiring. You go straight to the lines that change how things behave.

The rest is there when you want it.

Liked the review? Give MergeAtlas a star.

Star on GitHub

What the diff never showed

This is MergeAtlas on excalidraw/excalidraw#8613, which adds image cropping to the editor.

Exported images now come out cropped, yet no export code is in that diff. Here it sits right below the code that causes it.

The map's renderElement.ts card, changed in this pull request, with export.ts below it marked not changed but affected.

Map your next review

Open source, MIT. Works with any agent.

  1. Install

    Codex and other agents

    npx skills add ismayilkarimli/MergeAtlas

    or

    Claude Code

    /plugin marketplace add ismayilkarimli/MergeAtlas

    /plugin install mergeatlas@mergeatlas

  2. Ask your agent to map the pull request

    From inside the pull request's repository, ask your agent to map it or invoke it directly /mergeatlas:mergeatlas.

Star on GitHub