Gate OSS Patches With a Four-Check Review Packet

Description and use

A four‑gate packet ensures AI‑generated patches are reproducible, scoped, documented, and automatically reviewed, reducing reviewer effort and preventing regressions.

Problem

Maintainers struggle to ensure AI-generated patches are accurate, scoped, and documented before review, leading to wasted time and potential regressions.

Outcome

The workflow ensures every patch is accompanied by reproducible tests, scoped changes, and a documented review checklist, reducing reviewer effort and preventing regressions.

Workflow

• 1. Create a branch and add a focused repro test that reproduces the failure.
• 2. Commit the repro test and run it to confirm failure.
• 3. Add a scope lock script that allows only files listed in an allowlist.
• 4. Commit the scope lock and run it after each commit to prevent scope creep.
• 5. Write a review.json checklist manually, marking required items such as changelog entry and issue linkage.
• 6. Run the second reader AI prompt to automatically accept or reject the packet based on Gates 1‑3.
• 7. If accepted, merge the PR; if rejected, address the failed gates and repeat.

Evidence

Every outbound OSS change needs four artifacts on disk. They live beside the branch, not in chat history.

Source

Gate 1: lock the reproduction

Source

Gate 4: second reader, never author

Source