dependency-graph-analysis

Analyze code impact using AST-based dependency graphs before modifications.

Updated Oct 9, 2025
One-click install
npx skills add https://github.com/Siamese001/Agentic-Workflow --skill dependency-graph-analysis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dependency-graph-analysis
Source: https://github.com/Siamese001/Agentic-Workflow/tree/main/.windsurf/skills/dependency-graph-analysis
Command: npx skills add https://github.com/Siamese001/Agentic-Workflow --skill dependency-graph-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill prevents architectural drift and ensures code integrity by mandating AST-based dependency graph analysis before any code changes, eliminating risky guesswork and low-signal search methods.

Core Features & Use Cases

  • Mandatory Graph Analysis: Enforces the use of dependency graphs for impact analysis, root cause analysis, and file selection, ensuring a deep understanding of code relationships.
  • Fail-Closed Discipline: Guarantees that parsing failures halt execution and are explicitly reported, preventing silent fallbacks to unreliable text searches.
  • Use Case: Before modifying a critical service, use this Skill to generate a dependency graph, identify all upstream and downstream impacts, detect any architectural violations, and ensure all affected code has corresponding tests, preventing unintended regressions.

Quick Start

Use the dependency-graph-analysis skill to analyze the impact of changing the file '/path/to/your/code.py'.

Frequently Asked Questions about dependency-graph-analysis

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

FAQPage Schema
How do I perform AST-based dependency graph analysis for code impact assessment?▼

AST-based dependency graph analysis parses code structure to map relationships, enforcing graph-first discipline for impact assessment and root cause analysis before modifying files.

Why should I use a dependency graph instead of grep or regex for code investigation?▼

Dependency graphs provide high-signal architectural context by mapping structural relationships, whereas grep and regex rely on low-signal text matching that misses code integrity and architectural violations.

What happens if AST parsing fails during dependency graph construction?▼

If AST parsing fails, the fail-closed discipline halts execution and explicitly reports the error, preventing silent fallbacks to unreliable text searches that compromise code safety.

How do I analyze the impact of changing a specific file before modifying it?▼

To analyze the impact of changing a file, generate a dependency graph to identify all upstream and downstream impacts, detect architectural violations, and ensure affected code has corresponding tests.

Can I use this dependency graph analysis for root cause analysis and architectural drift prevention?▼

Yes, you can use dependency graph analysis for root cause analysis and preventing architectural drift by mandating structural relationship mapping before code changes to enforce code integrity.