codegraph
SolidGenerate a codebase knowledge graph with `graphify` at `graphify-out/` so other skills can query cross-file relationships before touching code. Do NOT use for runtime profiling.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- linkpranay-ai
- Repository
- linkpranay-ai/context-engineering-protocol
- Created
- 2 months ago
- Last Updated
- today
- Language
- Python
- License
- Apache-2.0
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
codebase-knowledge-graph
Use to keep codebase awareness current via graphify — a knowledge graph of modules, symbols, and dependencies used for impact analysis during change propagation. Trigger on "graphify", "update the code graph", "what depends on this", "impact of this change", or whenever a change needs a full picture of call sites and dependents. Detects whether graphify is installed; if not, offers to auto-install it or proceed with a lighter built-in fallback.
graphify
Use when the user invokes /graphify or asks to build, update, or query a knowledge graph from a folder of files (code, docs, papers, notes, images). Triggers: 'map this codebase', 'graph my notes', 'what is connected across these files', 'community detection', 'GraphRAG', incremental graph update, Neo4j/SVG/GraphML export, graph lookups (query, shortest path, explain a node). Not for simple file reads, vault edits, or plain text search.
graphify
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.