g1t/bench/reviewbench/Dockerfile
Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.
| Research: shipping CSS, and a ReviewBench harness for g1t's reviewer | 1 | # syntax=docker/dockerfile:1.7 |
| 2 | # | |
| 3 | # g1t's reviewer as a ReviewBench agent image: the g1t sandbox's base image | |
| 4 | # (the Claude Code CLI and toolchains production reviews run with) plus the | |
| 5 | # contract adapter in agent/. Built by `node bench/reviewbench/run.mjs build`, | |
| 6 | # which passes BASE from services/runner/base.json and regenerates | |
| 7 | # agent/instructions.txt from crates/runner/src/review.rs first. | |
| 8 | # | |
| 9 | # linux/amd64, as the contract requires. | |
| 10 | ||
| 11 | ARG BASE | |
| 12 | FROM --platform=linux/amd64 ${BASE} | |
| 13 | COPY agent/ /bench/ | |
| 14 | # /work/change.diff and /work/review.json are where the production prompt | |
| 15 | # tells the agent to read and write; the benchmark mounts the rest of /work. | |
| 16 | RUN mkdir -p /work && chmod 0777 /work | |
| 17 | ENTRYPOINT ["node", "/bench/agent.mjs"] |