Bloom Docs

Review code

Turn repeated review instructions into quick prompts, inspect every changed file and send precise feedback without leaving the workspace.

Review code with a quick prompt

A quick prompt is a reusable instruction, not a canned answer. Create one called Review code with the text below. It then sits beside every composer, ready to run against the workspace you are looking at.

Use the /review-code skill. Focus on correctness, regressions and missing tests. Do not change files.

Open Quick prompts, choose Review code and send it. The agent reviews the current branch in context. Keep variants for work you repeat, such as checking a migration, explaining a diff or preparing a release summary. A quick prompt can also ask Bloom to open a browser tab or split, so the review surface is ready before the answer arrives.

Reviewing the work

The right column lists what changed, against the merge base rather than against your last commit, so it shows the whole branch rather than the last thing the agent typed. Click a file to open its diff in the middle column, side by side or unified.

• Comment on a line and it goes back to the agent as part of your next message, with the file and line attached. This is the fastest loop in the app: read, mark the three lines you do not like, send.
• Edit the file yourself in the same view. Bloom refuses a save if the file changed on disk underneath you.
• Walk the files with ⌘⌥J and ⌘⌥K.
• Quick Look works on a changed file with the space bar, exactly as it does in Finder.