Skip to content
Skill

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, n

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
8.2K
Last commit
5 days ago
License
CC-BY-SA-4.0
Listing updated
today

When your agent uses it

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.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 6 files (12 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

This skill ships in the trailmark plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add trailofbits/skills
/plugin install trailmark@trailofbits

Or copy only this skill to ~/.claude/skills/trailmark-review-gate:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/trailofbits/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/trailmark-review-gate &&
cp -R "$tmp/plugins/trailmark/skills/trailmark-review-gate" ~/.claude/skills/trailmark-review-gate &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/trailmark-review-gate inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/trailmark-review-gate to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/trailofbits/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/trailmark-review-gate &&
cp -R "$tmp/plugins/trailmark/skills/trailmark-review-gate" ~/.agents/skills/trailmark-review-gate &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/trailmark-review-gate inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/trailmark-review-gate to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/trailofbits/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/trailmark-review-gate &&
cp -R "$tmp/plugins/trailmark/skills/trailmark-review-gate" ~/.cursor/skills/trailmark-review-gate &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/trailmark-review-gate inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/trailofbits/skills.git --path plugins/trailmark/skills/trailmark-review-gate

Or copy the folder to ~/.gemini/skills/trailmark-review-gate yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/trailmark-review-gate:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/trailofbits/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/trailmark-review-gate &&
cp -R "$tmp/plugins/trailmark/skills/trailmark-review-gate" ~/.copilot/skills/trailmark-review-gate &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/trailmark-review-gate inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/trailofbits/skills.git

Then copy skills/plugins/trailmark/skills/trailmark-review-gate into your agent's skills folder as trailmark-review-gate. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Trailmark review gate FAQ

How do I install Trailmark review gate in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/trailmark-review-gate to use it in all your projects, or to .claude/skills/trailmark-review-gate in one project. Or install the trailmark plugin, which includes it: /plugin marketplace add trailofbits/skills, then /plugin install trailmark@trailofbits.

Does Trailmark review gate run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Trailmark review gate?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

What are the best alternatives to Trailmark review gate?

The closest alternatives to Trailmark review gate are Rea changelog update, Code review, Gem devops guidelines, PR screenshots and Make repo contribution.

More from trailofbits/skills

  1. Runs a Trailmark summary analysis on a codebase

    • Open source
    • 8.2K GitHub stars
  2. Expands one confirmed or suspected vulnerability into a Trailmark graph neighborhood of variant candidates by finding sibling functions, sha

    • Open source
    • 8.2K GitHub stars
  3. Mutation-driven test vector generation

    • Open source
    • 8.2K GitHub stars
    • Knowledge and memory
  4. Hunts for the other instances of a bug already found — the variants of one root cause across a codebase

    • Open source
    • 8.2K GitHub stars
  5. This skill should be used when the user asks to "triage a vulnerability report", "assess a CVE", "evaluate a bug bounty submission", "decide

    • Open source
    • 8.2K GitHub stars
    • Security
  6. Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions

    • Open source
    • 8.2K GitHub stars

Alternatives to Trailmark review gate

  1. Prepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Ple

    • Open source
    • 465K GitHub stars
    • Developer tools
  2. Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's docu

    • Open source
    • 326K GitHub stars
    • Developer tools
  3. Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mo

    • Open source
    • 41.3K GitHub stars
    • Cloud and infrastructure
  4. Embed before/after screenshots and annotated images in pull request descriptions

    • Open source
    • 41.3K GitHub stars
    • Developer tools
  5. All changes to code must follow the guidance documented in the repository

    • Open source
    • 41.3K GitHub stars
    • Developer tools