trailmark review gate

AI Community

Skill notes

When to Use

Reviewing a branch, pull request, release diff, or fix commit Checking whether a change expands attack surface Looking for removed validation or authorization on reachable paths Comparing before/after taint, privilege-boundary, blast-radius, or complexity signals

When NOT to Use

Single-snapshot analysis. Use trailmark or trailmark-structural. Text-diff review only. Use differential-review. Full vulnerability discovery. Use an audit or bug-finding workflow. One static finding. Use trailmark-finding-triage. Tooling is unavailable and the user wants manual review only.

Rationalizations to Reject

Rationalization · Why It Is Wrong · Required Action "The line diff is small, so no graph gate is needed" · Small changes can create new call paths · Compare before/after graphs "Graph gate passed, so the PR is secure" · The gate only checks structural regressions · Still perform line-level review "Trailmark failed, so pass the gate" · Tool failure is unknown risk, not success · Emit UNKNOWN "Tests pass, so removed validation is fine" · Tests may miss affected entrypoint paths · Review the removed path manually

Step 1: Resolve Inputs

Accept two refs, a branch name, a commit range, or before/after directories. Do not check out branches unnecessarily. Prefer git diff, git show, and git worktrees, following the graph-evolution snapshot workflow.

Step 2: Build Graph Evidence

Run graph-evolution or equivalent Trailmark before/after graph analysis. Both snapshots must run engine.preanalysis() so taint, privilege-boundary, blast-radius, complexity, and entrypoint signals are available. Record Trailmark version and any feature probes. If graph construction fails, emit UNKNOWN.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@trailofbits · no license declared
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Resolve Inputs

Accept two refs, a branch name, a commit range, or before/after directories. Do not check out branches unnecessarily. Prefer `git diff`, `git show`, and git worktrees, following the `graph-evolution` snapshot workflow.

02
Step 2: Build Graph Evidence

Run `graph-evolution` or equivalent Trailmark before/after graph analysis. Both snapshots must run `engine.preanalysis()` so taint, privilege-boundary, blast-radius, complexity, and entrypoint signals are available. Record Trailmark version and any feature probes. If graph construction fails, emit `UNKNOWN`.

03
Step 3: Normalize Changes

Normalize evidence into: added, removed, and modified nodes added and removed edges entrypoint set changes taint membership changes

04
Step 4: Apply Gate Rules

Apply the rules in references/gate-rules.md. Gate verdicts are: Verdict · Meaning `FAIL` · A high-risk structural regression needs review before acceptance `WARN` · A meaningful graph change needs reviewer attention

05
Step 5: Emit Packet

Write the packet using references/output-format.md, then hand it to the branch reviewer. Use references/review-integration.md when combining this packet with `differential-review` or another PR review process.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.