initializing

Initialize grepai by configuring embedding provider, model, storage, and .gitignore.

1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/jugrajsingh/skillgarden --skill initializing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: initializing
Source: https://github.com/jugrajsingh/skillgarden/tree/main/plugins/grepai/skills/initializing
Command: npx skills add https://github.com/jugrajsingh/skillgarden --skill initializing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the setup of the grepai tool within a project, configuring essential settings like the embedding provider, model, and storage, while also ensuring proper integration with the project's version control.

Core Features & Use Cases

  • Project Initialization: Runs grepai init with specified or user-provided configurations.
  • Configuration Management: Sets up .grepai/config.yaml for embedding models and storage backends.
  • Version Control Integration: Automatically updates .gitignore to exclude the grepai index directory.
  • Workspace Support: Handles both single-project indexing and multi-project workspace configurations.

Quick Start

Initialize grepai for your project using the ollama provider and postgres backend.

Frequently Asked Questions about initializing

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

FAQPage Schema
How do I initialize grepai for a project to enable code indexing and retrieval?▼

To initialize grepai, run the setup process to configure the embedding provider, model, and storage backend, then update your .gitignore file to exclude the index directory. This ensures proper configuration for code indexing and retrieval.

Does grepai initialization support multi-project workspace configurations?▼

Yes, grepai initialization supports both single-project and multi-project workspace modes. This allows you to configure code indexing and retrieval across multiple projects simultaneously or individually as needed.

What configuration options are available when setting up grepai for code indexing?▼

When setting up grepai, you can configure the embedding provider, model, and storage backend. These settings are managed in the .grepai/config.yaml file to ensure proper setup for code indexing and retrieval.

Will initializing grepai automatically update my project's version control settings?▼

Yes, initializing grepai automatically updates the .gitignore file to exclude the grepai index directory. This ensures proper integration with your project's version control system during setup.

Can I use a postgres storage backend and ollama provider for grepai initialization?▼

Yes, you can initialize grepai for your project using the ollama provider and postgres backend. The setup process allows you to specify or provide these configurations for code indexing and retrieval.

What is the purpose of configuring an embedding model during project initialization?▼

Configuring an embedding model during project initialization sets up the necessary parameters for code indexing and retrieval. It defines how the grepai tool processes and stores code for efficient search.