edge-detection

Analyze code dependencies to detect integration edges and output an enriched knowledge graph.

2|Updated Mar 8, 2026

Search Tags:#architecture #code analysis #integration #knowledge graph #microservices #dependencies

Ready to run

npx skills add https://github.com/ran729/context-rot-skill --skill edge-detection

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: edge-detection
Source: https://github.com/ran729/context-rot-skill/tree/main/.claude/.claude/skills/edge-detection
Command: npx skills add https://github.com/ran729/context-rot-skill --skill edge-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies and visualizes the integration points (APIs, databases, queues, etc.) within your codebase, providing a clear map of your system's architecture and dependencies.

Core Features & Use Cases

Dependency Analysis: Scans code and dependency manifests to detect external services.
Pattern Recognition: Identifies common integration patterns (HTTP calls, database connections, message queues).
External Node Creation: Generates specific nodes for detected services (e.g., "S3 Bucket: user-uploads-prod") rather than generic ones.
Use Case: Understand how your microservices communicate by automatically discovering all REST API calls, database connections, and message queue interactions.

Quick Start

Use the edge-detection skill to analyze the codebase at '/path/to/your/project' and output the enriched knowledge graph to '/path/to/output/knowledge_graph.json'.

Frequently Asked Questions about edge-detection

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

FAQPage Schema

How do I map integration edges and external dependencies in my microservices architecture?▼

Mapping integration edges in microservices architecture requires analyzing code dependencies to detect external services like databases, queues, and APIs. This process identifies native integration patterns and generates specific nodes for each detected resource, creating an enriched knowledge graph of your system.

What is code dependency analysis for detecting external services and APIs?▼

Code dependency analysis for external service detection scans your codebase and dependency manifests to identify integration points. It recognizes common patterns like HTTP calls and database connections, creating specific nodes for detected cloud services, SDKs, and APIs rather than generic placeholders.

How do I visualize microservices dependencies and communication patterns automatically?▼

Visualizing microservices dependencies automatically involves detecting integration edges by analyzing code. This approach discovers REST API calls, database connections, and message queue interactions, outputting an enriched knowledge graph JSON that maps how your services communicate.

Do I need a knowledge graph JSON to analyze code dependencies and integration points?▼

A knowledge graph JSON is required as input to analyze code dependencies and integration points. The analysis uses this existing graph as a base, scanning your codebase to detect native integration patterns and outputting an enriched graph with specific nodes for external services.

Can code analysis detect specific cloud services and SDKs rather than generic connections?▼

Code analysis detects specific cloud services and SDKs by recognizing native integration patterns and dependencies. It identifies external resources like S3 buckets or message queues, generating specific nodes for each detected service in the enriched knowledge graph output rather than generic connection placeholders.

What types of integration patterns can be identified through code dependency analysis?▼

Integration patterns identified through code dependency analysis include HTTP calls, database connections, message queues, cloud services, and SDKs. The analysis detects these native patterns by scanning code and dependency manifests, creating specific nodes for each external resource in the knowledge graph.