graph-evolution

Compare Trailmark code graphs between two source snapshots to detect security-relevant structural changes.

Updated May 2, 2026
One-click install
npx skills add https://github.com/ayehiaa/my-travel-assistant --skill graph-evolution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graph-evolution
Source: https://github.com/ayehiaa/my-travel-assistant/tree/main/.agents/skills/graph-evolution
Command: npx skills add https://github.com/ayehiaa/my-travel-assistant --skill graph-evolution

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires trailmark, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you detect security-relevant structural changes between two code snapshots that are easy to miss with line-by-line diffs, such as new attack paths, taint propagation changes, blast radius growth, and privilege boundary modifications.

Core Features & Use Cases

  • Structural graph comparison across snapshots: Build Trailmark code graphs for a “before” and “after” snapshot and compute a structural diff.
  • Security-focused evolution signals: Identify new tainted paths, entrypoint and trust changes, blast radius shifts, complexity deltas, and privilege boundary changes.
  • Complementary to text diffs: Use it to complement differential reviews by focusing on architecture/flow-level changes rather than superficial edits.

Quick Start

Use the graph-evolution skill to compare two git refs by building Trailmark graphs for each, running pre-analysis on both, computing the native structural diff and the subgraph diff, then reviewing the generated security-focused report.

Frequently Asked Questions about graph-evolution

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

FAQPage Schema
How do I detect new attack paths when comparing two code snapshots?

Detect new attack paths by building Trailmark code graphs for both snapshots, running pre-analysis, and computing structural graph diffs to surface taint propagation changes and new tainted paths.

What is security-relevant code evolution analysis?

Security-relevant code evolution analysis identifies structural changes between source snapshots, such as blast radius growth, privilege boundary modifications, and trust changes, that line-by-line text diffs easily miss.

Does graph-evolution work with git branches and tags for pre-release audits?

Yes, it works for audit and pre-release comparisons across commits, tags, branches, or directories, computing both native structural diffs and subgraph membership diffs from exported JSON.

How do I compute a structural graph diff between two commits?

Compute a structural graph diff by building Trailmark graphs for each snapshot, running engine.preanalysis() on both, and executing graph_diff.py on the exported JSON to compare subgraph membership.

Do I need the trailmark dependency to analyze taint propagation changes?

Yes, the trailmark dependency is required to build the underlying code graphs and run the pre-analysis needed to detect taint propagation changes and blast radius shifts.

What's the best way to review code evolution for security risks?

The best way to review code evolution for security risks is complementing text diffs with structural graph comparisons, focusing on architecture-level attack path detection and privilege boundary changes rather than superficial edits.