AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

trailmark-review-gate

Runs a Trailmark structural review gate over a branch, pull request, fix commit, release diff, or git ref range to detect new entrypoints, new tainted paths, removed validation or authorization calls, privilege-boundary drift, blast-radius growth, complexity growth, and newly reachable sensitive sinks. Use when reviewing a PR, branch, remediation commit, or release diff where graph-level security regressions should be checked before merge.

Original source
trailofbits
License
CC-BY-SA-4.0
Pinned revision
2be6433b39e009cd2b6fd3be1895f6b1faa5af9a

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read trailofbits--trailmark-review-gate at revision 2be6433b39e009cd2b6fd3be1895f6b1faa5af9a, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 4

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:

  1. Run differential-review to identify risky changed files and functions.
  2. Run graph-evolution and trailmark-review-gate on the same before/after range.
  3. Cross-reference FAIL and WARN rules with changed source lines.
  4. Add the gate packet to the review notes.
  5. Treat PASS as "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 UNKNOWN if graph evidence cannot confirm the structural change

This does not replace semantic verification that the original finding was fixed.