context-graph

Store decision traces and query past precedents via semantic search.

9|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ingpoc/SKILLS --skill context-graph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-graph
Source: https://github.com/ingpoc/SKILLS/tree/main/context-graph
Command: npx skills add https://github.com/ingpoc/SKILLS --skill context-graph

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires voyageai, chromadb, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Context-Graph provides a living record of decisions and their outcomes, enabling teams to recall past choices, justify actions, and learn from history.

Core Features & Use Cases

  • Storing decision traces with timestamps and metadata (category, feature_id, state, session) to build a searchable memory.
  • Semantic search across traces using Voyage AI embeddings to find precedents by meaning, not keywords.
  • Pattern extraction and learning loops to surface recurring decision patterns and support reflexion-style improvements.
  • Use cases include retrospective debugging, decision auditing, and cross-project knowledge management.

Quick Start

Store a decision trace with context and immediately query for similar precedents to validate the decision.

Frequently Asked Questions about context-graph

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

FAQPage Schema
How do I store decision traces for semantic search and precedent retrieval?

You can store decision traces with timestamps and metadata like category and session state. This builds a searchable memory for precedent retrieval, enabling semantic search across past decisions to validate current choices.

What is semantic search across past precedents using vector embeddings?

Semantic search across past precedents uses Voyage AI vector embeddings to find similar historical decisions by meaning rather than exact keywords. This enables teams to recall past choices and justify actions based on contextual similarity.

Do I need Voyage AI and ChromaDB to run context-graph for memory management?

Yes, Voyage AI and ChromaDB are required dependencies. Voyage AI generates vector embeddings for semantic search, while ChromaDB serves as the vector store for querying stored decision traces and past precedents.

Can I extract recurring decision patterns for learning loops across projects?

Yes, pattern extraction surfaces recurring decision patterns to support reflexion-style improvements. This enables learning loops across multiple projects by analyzing historical decision traces stored with metadata.

What's the best way to audit cross-project decisions using a vector store?

The best way to audit cross-project decisions is storing traces with rich metadata like feature_id and state in a vector store. ChromaDB then enables semantic retrieval of past precedents for retrospective debugging and decision auditing.

Why use semantic search for decision traces instead of keyword matching?

Semantic search finds precedents by meaning rather than exact keywords, retrieving contextually similar past decisions even when terminology differs. This prevents missing relevant historical outcomes during debugging or learning loops.