code-knowledge-graph

Solid

Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.

AI & Automation 501 stars 42 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 94/100

Stars 20%
90
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Code Knowledge Graph - Codebase Graph Analysis Codebase'i knowledge graph olarak modeller. Dosya, modul, fonksiyon ve class'lar node; import, call, inheritance ve composition iliskileri edge olur. Sonuc: Mermaid diagram + JSON graph data. ## Neden Knowledge Graph? Kod text degil, **graph**'tir. Her dosya diger dosyalara baglidir. Bu baglantilari anlamadan: - Refactoring yaparken neyi kiracagini bilemezsin - Dead code'u guvenle silemezsin - Yeni feature'in nereye oturacagini gormezsin - Circular dependency'lerin kokunu bulamazsin Knowledge graph tum bu iliskileri gorsellestirir ve olculebilir yapar. ## Kullanim ``` /code-knowledge-graph [hedef-dizin] [--focus module] [--depth N] [--format mermaid|json|both] ``` ### Ornekler ```bash # Tum codebase analizi /code-knowledge-graph src/ # Belirli module odaklan /code-knowledge-graph src/ --focus auth # Sadece circular dependency kontrolu /code-knowledge-graph src/ --focus circular # Hotspot analizi /code-knowledge-graph src/ --focus hotspots # Orphan/dead code tespiti /code-knowledge-graph src/ --focus orphans ``` ## Graph Olusturma Adimlari ### Adim 1: Node Discovery ```bash # Dosya agaci tldr tree ${PATH:-src/} --ext .py # Kod yapisi: fonksiyonlar, class'lar, export'lar tldr structure ${PATH:-src/} --lang python ``` Her dosya, class, fonksiyon ve export bir **node** olur. ### Adim 2: Edge Extraction ```bash # Dosyanin import'lari (outgoing edges) tldr im...

Details

Author
vibeeval
Repository
vibeeval/vibecosystem
Created
2 months ago
Last Updated
yesterday
Language
C#
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category