graph-evolution

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

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/rohanbhatia27/rohanstutoring-redesign --skill graph-evolution-rohanbhatia27
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graph-evolution
Source: https://github.com/rohanbhatia27/rohanstutoring-redesign/tree/main/.agents/skills/graph-evolution
Command: npx skills add https://github.com/rohanbhatia27/rohanstutoring-redesign --skill graph-evolution-rohanbhatia27

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Detects security-relevant structural changes in code graphs, identifying vulnerabilities that text diffs may miss.

Core Features & Use Cases

  • Security-Driven Analysis: Identifies new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications.
  • Code Evolution: Compares Trailmark code graphs at different source code snapshots (commits, tags, or directories).
  • Use Case: Use this Skill to compare code changes between commits for security-relevant evolution, detecting new attack paths, or finding security-relevant changes missed by text diffs.

Quick Start

Run the graph-evolution skill to compare code between two git commits.

Frequently Asked Questions about graph-evolution

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

FAQPage Schema
How do I detect security vulnerabilities in code changes that text diffs miss?

Analyze code graph evolution between two source code snapshots to detect security-relevant structural changes. This approach identifies new attack paths, taint propagation changes, and privilege boundary modifications that traditional text-based diffs overlook.

What is code graph evolution analysis for security?

Code graph evolution analysis compares Trailmark code graphs across different source code snapshots to identify security-relevant structural changes. It detects new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications.

How do I compare code between two git commits for security-relevant changes?

Run the graph-evolution analysis on Trailmark code graphs built from two git commits. It compares the structural differences between snapshots to identify new attack paths, complexity shifts, and taint propagation changes.

Do I need Trailmark to analyze code graph evolution?

Yes, Trailmark is required for code graph building and pre-analysis. The graph-evolution analysis depends on Trailmark code graphs to detect security-relevant structural changes between source code snapshots.

What security-relevant structural changes can code graph analysis identify?

Code graph analysis identifies new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications between two source code snapshots. These structural changes often reveal vulnerabilities missed by text diffs.

Can I use code graph analysis to track blast radius growth across commits?

Yes, comparing Trailmark code graphs between source code snapshots detects blast radius growth along with new attack paths and taint propagation changes. This reveals how structural code evolution expands the potential impact of vulnerabilities.