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.

Источник