Derive OSS Review Scope From the Crash Transcript

说明与用途

修补程序审查仅限于崩溃转储中引用的文件，避免无关更改并确保评论引用特定日志行。

问题

Patch reviews often drift into unrelated code changes when the review scope is not tied to the actual failure reported in a crash transcript.

结果

The gate confines patch reviews to the exact files involved in the crash, reducing noise and ensuring that review comments are grounded in the reproduction transcript.

工作流

• 1. Freeze a disposable worktree at the issue SHA using git worktree add.
• 2. Capture a reproduction transcript by running the failing command and logging stdout, stderr, and exit code.
• 3. Parse the transcript to extract source file paths from stack frames, filtering out virtualenv and generated files.
• 4. Store artifacts: worktree.lock, repro.cmd, transcript.txt, scope.paths.
• 5. Enforce the gate: only files listed in scope.paths (plus tests) may be modified; review comments must reference transcript.txt lines.
• 6. If reproduction succeeds (exit code 0), abort the review before any model sees the diff.

证据

OSS patch review should start from a crash transcript. The transcript defines files, claims, and comments.

来源

The gate writes four local artifacts. Each file is small and replayable.

来源