grepai-storage-gob_skill

This skill configures GrepAI to use GOB local file storage for embeddings, metadata, and indexes, enabling simple single-machine setups.

1

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill yoanbernabeu/grepai-skills --skill grepai-storage-gob

SKILL.md5.2 KB

Overview

This skill configures GOB local file storage as the backend for GrepAI, the default and simplest option for single-machine setups. It stores embeddings, file metadata, and chunk information in a single .grepai/index.gob file. Use it for quick, private, zero-dependency indexing and search on small to medium codebases.

How this skill works

GOB uses Go's binary serialization to write the entire index into files under .grepai/ (index.gob and symbols.gob). On search, the index is loaded into RAM for fast, low-latency queries. Configuration is minimal—set store.backend: gob—and GrepAI creates and updates the local file when you run grepai init and grepai watch.

When to use it

Local development on a single machine
Small to medium-sized repositories (up to ~10K files)
When you want no external services or infrastructure
Quick start or proof-of-concept for semantic code search
When privacy and portability (single-file backup) matter

Best practices

Add .grepai/ to .gitignore to avoid committing the index
Backup .grepai/index.gob before major experiments or upgrades
Re-index after changing the embedding model to keep vectors consistent
Monitor index size and RAM usage; migrate if it approaches ~1 GB
Prefer per-developer local indexes rather than sharing files across machines

Example use cases

A solo developer enabling semantic code search on a personal repo
Small team prototyping GrepAI features without deploying a server
Local codebase analysis and call-graph lookups during development
Fast iterations on embeddings and indexing without external dependencies
Temporary indexing on CI runner for isolated tests

FAQ

Sharing is unsupported in practice: the file is tied to the embedding model, absolute file paths, and specific code versions. Each developer should run their own grepai watch.

When should I migrate from GOB to a hosted backend?

Migrate when your index grows beyond ~1 GB, you need concurrent access, want to share an index across machines, or have tens of thousands of files—use PostgreSQL or Qdrant for scalability and sharing.