review-followup

Verify blocking issues from a previous GitLab code review by performing a follow-up review that checks the merge request sequentially, ensuring original problems are resolved and no regressions were introduced. A concise report is then posted back to the MR.

A follow-up code review is a secondary verification step needed after a developer submits corrections to a merge request. It confirms previously identified blocking issues are fixed and detects new regressions before the code is merged.

Yes, a follow-up merge request review requires MCP tools to manage GitLab threads. Specifically, it uses get_threads, add_action, and set_phase to fetch existing discussions, post verification actions, and enforce a strict publication order for the final report.

Post a concise follow-up report to a GitLab MR by executing review steps sequentially to prevent memory spikes, checking for regressions, and using MCP tools to publish the final report directly to the merge request thread.

The best way to automate code review follow-up checks without memory spikes is to execute verification steps sequentially rather than in parallel, systematically checking resolved blocking issues and new regressions before generating a report.

The follow-up review process enforces a strict publication order to ensure thread actions and phase updates are applied correctly on GitLab before the final markdown report is published, preventing incomplete or out-of-sequence review statuses.