references/review-integration.md
Review Integration
Use the review gate packet as supporting evidence for a human branch review. It should be attached to, pasted into, or summarized alongside line-level review notes.
With Differential Review
Use differential-review for line-level analysis and this skill for structural
signals. Recommended order:
- Run
differential-reviewto identify risky changed files and functions. - Run
graph-evolutionandtrailmark-review-gateon the same before/after range. - Cross-reference
FAILandWARNrules with changed source lines. - Add the gate packet to the review notes.
- Treat
PASSas "no configured graph rule fired", not as approval.
With PR Review Processes
When an engagement has a separate PR review workflow, include:
- gate verdict
- triggered rules table
- exact changed nodes and paths
- manual reviewer actions
- limitations
Do not use GitHub write actions unless the review process explicitly asks for them. The packet is review evidence, not an automatic merge decision.
With Remediation Review
For a fix commit:
- compare vulnerable base to the proposed fix
- check that affected reachable paths changed as expected
- check that no new entrypoint or sensitive-sink path appeared
- report
UNKNOWNif graph evidence cannot confirm the structural change
This does not replace semantic verification that the original finding was fixed.