grepai-workspaces_skill

This skill helps you manage multi-project codebases with unified search across workspaces, enabling monorepos, microservices, and cross-project queries.

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-workspaces

SKILL.md8.3 KB

Overview

This skill helps you configure and manage multi-project workspaces in GrepAI so related repositories can share a unified search index and configuration. It streamlines indexing, cross-project semantic search, and workspace-level status and configuration. Use it to organize monorepos, microservices, or any set of related projects you want to query together.

How this skill works

You create a named workspace and add project paths to it; GrepAI stores workspace config under ~/.grepai/workspaces/<name> and builds a combined index and symbols store. Run grepai watch --workspace <name> to index all projects (foreground or background), then search across the entire workspace or limit queries to a single project with --project. The workspace also exposes status, listing, removal, and deletion commands so you can manage the index and daemon per workspace.

When to use it

Managing a monorepo with many packages that should be searchable together
Exploring dependencies across microservices or separate services
Keeping frontend, backend, and shared libraries in one searchable context
Maintaining a combined semantic index for related projects
Running an MCP server or daemon scoped to a logical project group

Best practices

Name workspaces descriptively (e.g., ecommerce-stack) for clarity
Group only related projects you commonly search together to reduce noise
Run a single watcher per workspace (grepai watch --workspace) to keep indexes up to date
Re-index after major refactors, adds, or removals to keep search accurate
Use the --project filter when you want focused results from one codebase

Example use cases

Create a monorepo workspace and add web, mobile, and shared packages for unified search
Bundle related microservices into a services workspace to trace cross-service calls
Combine frontend, backend, and shared-types into a fullstack workspace for end-to-end queries
Run grepai watch --workspace my-workspace --background to keep a long-running indexer
Use grepai search --workspace services "REST API endpoint handler" to locate handlers across services

FAQ

Run grepai workspace remove <workspace> /old/path then add the new path with grepai workspace add <workspace> /new/path.

Does deleting a workspace remove my project files?

No. Deleting a workspace removes its configuration and combined index but does not delete project source files.