trailmark-review-gate

Applies structural gate rules to Trailmark graph diffs to detect security regressions in branches and pull requests.

6.9k|598|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/trailofbits/skills --skill trailmark-review-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trailmark-review-gate
Source: https://github.com/trailofbits/skills/tree/main/plugins/trailmark/skills/trailmark-review-gate
Command: npx skills add https://github.com/trailofbits/skills --skill trailmark-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Line-level diffs often miss graph-level security regressions such as new entrypoints, removed authorization checks, or newly reachable sensitive sinks. This Skill turns Trailmark before/after graph evidence into a deterministic review gate with PASS, WARN, FAIL, or UNKNOWN verdicts.

Core Features & Use Cases

  • Structural Gate Rules: Detects new untrusted entrypoints, new tainted paths to sensitive sinks, removed validation or authorization calls, privilege-boundary drift, blast-radius growth, and complexity growth.
  • Deterministic Verdicts: Emits FAIL, WARN, PASS, or UNKNOWN with conservative default thresholds and explicit rule precedence, never reporting PASS when tooling fails.
  • Review Packet Output: Produces a structured Markdown packet with triggered rules, changed nodes, and reviewer actions that integrates with differential-review and PR workflows.
  • Use Case: Before merging a remediation commit, compare the vulnerable base against the fix to confirm no new entrypoint or sensitive-sink path appeared and that removed validation is flagged for manual review.

Quick Start

Run the Trailmark review gate on this pull request's before and after refs and give me the gate verdict with any triggered rules.

Frequently Asked Questions about trailmark-review-gate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check a pull request for structural security regressions?

Run graph-evolution on the before and after refs, then apply the review gate rules to the normalized changes. The gate emits FAIL, WARN, PASS, or UNKNOWN with exact changed nodes and paths for each triggered rule.

What does the Trailmark review gate detect in a code diff?

It detects new untrusted entrypoints, new tainted paths to sensitive sinks, removed validation or authorization calls, privilege-boundary drift, blast-radius growth, complexity growth, and new unresolved or dynamic calls on reachable paths.

Can the review gate replace line-level code review?

No. The gate only checks structural graph regressions and produces evidence for reviewers. It should be combined with line-level analysis such as differential-review, and a PASS verdict never means the change is secure.

What happens when Trailmark fails to build the graph?

The gate emits an UNKNOWN verdict instead of PASS, because tool failure represents unknown risk rather than success. Suspected fail conditions are listed as manual review targets alongside the UNKNOWN verdict.

When should I not use a graph-based review gate?

Skip it for single-snapshot analysis, text-diff-only review, full vulnerability discovery, or triage of one static finding. Those cases are better served by trailmark, differential-review, audit workflows, or finding triage respectively.