Skip to content
B/MSBUILD. TRAIN. PLAY.
Let’s talk ↗
BADRISH / EXPLORE
All projects

05 / Sandboxed fixes, developer approval

Agentic code review

The agent reviews pull requests and tests fixes in Docker sandboxes. It requires developer approval to post or merge.

Project
Independent project
My role
Builder
A keyboard and monitor on a dark desk.
Code review with a developer in control. Illustrative photograph.Nikita Kachanovsky · Unsplash License. Resized and converted to WebP.

Purpose

Test fixes. Get developer approval.

The agent reviews pull requests and tests proposed fixes in Docker sandboxes. Testing a fix does not permit the agent to post a review or merge. It requires developer approval for those actions.

Process

How it works.

  1. The implementation

    Test fixes in Docker sandboxes.

    The pull-request review agent tests fixes in Docker sandboxes.

  2. The approval boundary

    Require developer approval.

    The workflow requires developer approval before the agent posts or merges.

Evidence

The implementation.
Its scope.

  • The agent reviews pull requests.
  • It tests proposed fixes in Docker sandboxes.
  • It requires developer approval before posting or merging.

Scope. An agent workflow for code review. Proposed fixes run in Docker. Posting a review or merging requires developer approval.

Tools

The stack.

  • Docker
Explore the project films

Scroll through a scene, or move its slider. The transcript explains each step.

The idea, in motion.

AI-generated visual study. Illustrative interface.

Agentic code review: Review the proposed code change.

Scroll to explore. Use the slider to choose a moment.

Read the scene transcript
  1. 0:00–0:05
    Review the proposed code change.

    A proposed fix still needs a check.

An agent workflow for code review. Proposed fixes run in Docker. Posting a review or merging requires developer approval.

Follow the workflow.

Workflow illustration. Sample data.

Agentic code review: Review the proposed code change.

Scroll to explore. Use the slider to choose a moment.

Read the scene transcript
  1. 0:00–0:06
    Review the proposed code change.

    A proposed fix still needs a check.

  2. 0:06–0:12
    Test the fix in a Docker sandbox.

    Keep the test run separate from the review.

  3. 0:12–0:18
    Inspect the test output.

    Use the output to assess the proposed fix.

  4. 0:18–0:24
    Ask the developer for approval.

    Approval is required before posting or merging.

  5. 0:24–0:30
    Test first. Let the developer decide.

    Keep testing and approval as separate steps.

An agent workflow for code review. Proposed fixes run in Docker. Posting a review or merging requires developer approval.

Image credits