patch-diff
Installation
SKILL.md
Patch Diff (N-day recovery from vendor fixes)
Under an authorized engagement, recover a vulnerability from the fix that closed it: obtain the before and after builds, align symbols, diff the binaries, read the added checks to infer the bug class, then prove the bug with a PoC that reproduces on the unpatched build and runs clean on the patched one. The standing finding quality gates and the adversarial gate in your system prompt apply throughout: a crash you cannot reproduce on demand is a hypothesis, not a finding.
Attribution: adapted from the patch-diff-exploit playbook of zhaoxuya520/reverse-skill (MIT License).
Boundaries and authorization
| Allowed | Prohibited |
|---|---|
| Diffing and testing builds in your own lab, on machines covered by written engagement scope, or inside CTF and benchmark ranges | Running a recovered PoC against systems you do not own, even when a program covers the underlying bug |
| Writing PoCs that demonstrate the bug (crash, hang, memory-corruption evidence) | Turning a PoC into a deliverable payload |
Publishing or reporting with {target}, {host}, {user} placeholders |
Publishing unredacted hostnames, IPs, or usernames |
If the environment lacks a tool a step needs (see Environment notes), report the gap and stop. Never simulate diff output or fabricate crash evidence.