Scenario
When users ask AI to review or understand a codebase, the most common bottleneck is not the review itself but the "feeding": repos run to tens of thousands of lines, the AI context window is limited, and dragging the whole thing in either blows the limit or drops parts. This combo chains "feed code β review β sandbox verification" into a deterministic pipeline: repomix packs the repo into a single file (token-controlled), code-review-graph produces review conclusions, then swe-rex executes code / runs tests in a sandbox to verify those conclusions. Each of the three tools owns one stage, no overlap.
Combo members
repomix: code context packing (input side)
- Download: npm package
repomix; GitHub Release single binary (no Node needed); brew (macOS) - Version: >= 1.18.0 (measured 2026-08-29; Node >= 18)
- Install:
npm_config_registry=https://registry.npmmirror.com npm install -g repomix
repomix <repo-dir> --output repomix-output.txt --compress
code-review-graph: review (analysis side)
- Download: PyPI
code-review-graph(official recommendation pipx; China uses the Tsinghua mirror) - Version: == 2.3.8 (measured version recorded 2026-08-28)
- Install:
pip install -i https://pypi.tuna.tsinghua.edu.cn/simple code-review-graph==2.3.8
swe-rex: sandbox execution verification (output side)
- Download: PyPI
swe-rex(official) - Version: == 1.4.0 (measured version recorded 2026-08-28)
- Install:
pip install -i https://pypi.tuna.tsinghua.edu.cn/simple swe-rex==1.4.0
Install order
- repomix (packing) β 2. code-review-graph (review) β 3. swe-rex (fixing); the combo is ready only when all three are installed and running. All three are CLI tools, no server, no background process.
Dependency warnings
- Node >= 18 (repomix npm form); Python 3.10+ (crg/swe-rex, isolated venv recommended)
- repomix output file should be added to .gitignore (prevent the packed file from entering the repo)
- Large-repo token budget:
--compress+--includecontrol scope; measured: packing the full site docs directory produced 62KB/959 lines - Conflicts: the three tools' write surfaces do not overlap (output file / review report / sandbox execution environment) β compatible (combo measured state)
Acceptance check (one shot)
Run this block after installing; all green = combo ready; any failure -> back to the matching step in the install walkthrough.
repomix --version
code-review-graph --version
swerex-remote --help
ι’ζθΎεΊ: repomix >= 1.18.0; code-review-graph 2.3.8; swerex-remote prints usage. All green = package -> review -> sandbox command surface ready
Note: member-level commands measured (repomix pack measured 62KB/959 lines); real sandbox execution needs Docker (not measured at combo level, honestly marked).
Verification evidence
Every combo is measured in an isolated environment (smoke + write-surface check); unmeasured items are honestly marked in the text, and measurement dates are listed in the verification section below.
Verified 2026-08-29 Β· TTL expires β (180 days)
- 2026-08-29: repomix 1.18.0 measured packing success (smoke log: 62KB/959 lines, seconds)
- 2026-08-28: code-review-graph installed via Tsinghua mirror venv with 159 packages + command surface measured (handbook); swe-rex recorded and measured (handbook)
- Full chain (pack β review β sandbox verification) to be measured at combo acceptance (each tool verified separately; swe-rex sandbox needs Docker, pending in this environment)
Related problems
β All combos ο½ Tool Catalog ο½ Hit a problem? Submit a helpdesk card