basemind

Index and query large codebases for structural insight without reading files.

75|13|Updated Jun 1, 2024
One-click install
npx skills add https://github.com/Goldziher/basemind --skill basemind
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: basemind
Source: https://github.com/Goldziher/basemind/tree/main/opencode-plugin/skills/basemind
Command: npx skills add https://github.com/Goldziher/basemind --skill basemind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Basemind provides contextual understanding of a repository by indexing code, docs, history, and memory so agents can answer structural questions without reading raw files.

Core Features & Use Cases

  • Outline and symbol search across languages
  • Reference/caller lookups, call graphs, and implementations
  • Git history, blame, and diffs at symbol level
  • Document processing with semantic search across formats
  • Shared memory per-repo with cross-session persistence
  • Web crawl for on-demand context augmentation

Quick Start

Run basemind scan to index the repository, then query for definitions, references, or recent changes.

Frequently Asked Questions about basemind

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

FAQPage Schema
How do I search for symbol definitions across a multi-language codebase without reading raw files?

To search for symbol definitions across large codebases without reading raw files, index the repository to build structural outlines and symbol graphs for cross-language navigation. This provides instant context and structural insight for locating definitions quickly.

Can I trace call graphs and caller references in a large repository without loading the entire source?

Yes, you can trace call graphs and caller references by indexing the repository to build a structural symbol graph. This allows agents to examine implementations and follow call graphs without loading the entire source code into context.

What is the best way to examine git history and blame at the symbol level?

The best way to examine git history and blame at the symbol level is to index the repository with a structural code navigation tool. This enables querying of git history, blame, and diffs directly at the symbol level without reading raw files.

Does semantic document indexing work with cross-session memory sharing for code navigation?

Yes, semantic document indexing works with cross-session memory sharing by maintaining shared memory per repository. This allows contextual understanding and structural insights to persist and be reused across multiple agent sessions.

How do I index a repository to start querying for definitions and recent code changes?

To index a repository and start querying for definitions and recent changes, run a scan command to process code, docs, and git history. Once indexed, you can query for symbol definitions, references, and diffs without reading raw files.