Patch Review Workbench
Review an existing unified diff file by file and hunk by hunk. The workbench compares declared line coordinates and context exactly with supplied text, previews the result in memory and applies reverse hunks to verify restoration.
Key features
- Validate line ranges and changes across files and hunks
- Match context and final newlines exactly
- Show expected/actual text and a nearby diagnostic offset
- Preview text creation/deletion and consistent CRLF sources
- Download changed text, JSON and reverse patch
How to use
- Paste a patch or choose a .diff file.
- Supply original text for each path or import local files.
- Check applicability and inspect each hunk error.
- Review changed text and reverse round-trip result.
- Download only the results you need.
Use cases
- Check a received code patch against current text
- Locate context conflicts in documentation patches
- Review changes across configuration files
- Verify exact restoration through a reverse patch
Frequently asked questions
Does it modify repository files?
No. It processes supplied text in browser memory and runs no Git or shell patch command.
Will it always match git apply?
No. This strict subset requires exact coordinates and context. Fuzzy/3-way, binary, rename and mode changes are unsupported.
Will nearby matching context apply automatically?
No. Nearby matches are diagnostic only; the declared position stays mandatory.
Does it handle EOF and CRLF?
Yes. It verifies final no-newline markers and preserves consistently CRLF source text.
What does reverse verification mean?
The opposite-direction hunks restore the exact supplied original from the in-memory result.
Privacy
Patch and source text remain in browser memory. Downloaded previews and reverse patches can contain real file contents.
Comments & questions