knowledge-graph

Create markdown knowledge graphs linking modules, decisions, and conventions with wiki links.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/JNZader/javi-ai --skill knowledge-graph-jnzader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-graph
Source: https://github.com/JNZader/javi-ai/tree/main/own/skills/knowledge-graph
Command: npx skills add https://github.com/JNZader/javi-ai --skill knowledge-graph-jnzader

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Maintain markdown-based codebase knowledge graphs with [[wiki links]] and navigable engram relationship linking. Trigger: When documenting codebase architecture, linking related concepts, auditing knowledge consistency, or building structural memory beyond session-level.

Core Features & Use Cases

  • Create, interlink, and navigate architectural concepts (modules, responsibilities, decisions) to form a graph of your codebase.
  • Persist and traverse relationships with wiki-style links to enable quick onboarding and structural audits.
  • Audit knowledge integrity by linking concepts to code structure and documenting architectural rationale.

Quick Start

Document a new architecture concept by creating a .knowledge entry and link it to related concepts.

Frequently Asked Questions about knowledge-graph

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

FAQPage Schema
How do I document codebase architecture using a knowledge graph?

Document codebase architecture by creating entries for modules and design decisions, then interlink them into a knowledge graph. This organizes architectural concepts and persists relationships for long-term recall and quick onboarding.

Can I use wiki links to cross-reference architectural concepts in markdown?

Yes, you can cross-reference architectural concepts in markdown using wiki-style links. This creates a navigable graph of module responsibilities, dependencies, and design rationale across your codebase.

What is the best way to audit codebase knowledge consistency and structural dependencies?

The best way to audit codebase knowledge consistency is by linking architectural concepts to code structure and documenting design rationale. This enables structural audits by traversing persisted relationships within the knowledge graph.

Does this approach require a specific template for documenting module responsibilities?

Yes, documenting module responsibilities requires a consistent entry template. This enforces structural consistency across the codebase knowledge graph, ensuring that architectural decisions and conventions are uniformly recorded.

How do I maintain long-term recall of architectural decisions across multiple codebases?

Maintain long-term recall of architectural decisions by applying the knowledge graph across codebases. It persists module relationships and design rationale beyond session-level memory, enabling continuous structural documentation.