graph-evolution

Identify security-relevant structural changes in code graphs between git commits.

Updated Jun 9, 2026

Search Tags:#git #code analysis #security #evolution #code graph

Ready to run

npx skills add https://github.com/iiammae/opero --skill graph-evolution-iiammae

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: graph-evolution
Source: https://github.com/iiammae/opero/tree/main/.agents/skills/graph-evolution
Command: npx skills add https://github.com/iiammae/opero --skill graph-evolution-iiammae

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies security-relevant structural changes in code graphs, detecting issues that text diffs miss, such as new attack paths and complexity shifts.

Core Features & Use Cases

Security-Relevant Analysis: Detects new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications.
Use Case: Compare code between commits or tags to find security-relevant changes that text diffs miss, such as new attack paths or increased complexity.

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 new attack paths in code between git commits?▼

To detect new attack paths in code between git commits, you can analyze code graph evolution to identify security-relevant structural changes that text diffs miss. This includes spotting new attack paths, taint propagation changes, and privilege boundary modifications.

What security-relevant structural changes can code graph evolution analysis find?▼

Code graph evolution analysis finds security-relevant structural changes such as new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications that traditional text diffs often miss.

Do I need trailmark to analyze code graph evolution for security changes?▼

Yes, you need trailmark to analyze code graph evolution because it is required for building and analyzing the code graphs used to identify security-relevant changes between git commits or tags.

Can I use code graph analysis for codebase security audits?▼

Yes, you can use code graph analysis for codebase security audits by comparing code between commits or tags. It detects structural changes like increased complexity and blast radius growth that introduce security vulnerabilities.

Why does text diff miss security-relevant changes that code graph evolution detects?▼

Text diff misses security-relevant changes because it only shows line-level modifications, whereas code graph evolution analysis maps structural relationships to detect new attack paths, complexity shifts, and blast radius growth across the codebase.