grepai-quickstart
Get started with GrepAI in 5 minutes. Use this skill for a complete walkthrough from installation to first search.
What this skill does
# GrepAI Quickstart
This skill provides a complete walkthrough to get GrepAI running and searching your code in 5 minutes.
## When to Use This Skill
- First time using GrepAI
- Need a quick refresher on basic workflow
- Setting up GrepAI on a new project
- Demonstrating GrepAI to someone
## Prerequisites
- Terminal access
- A code project to index
## Step 1: Install GrepAI
### macOS
```bash
brew install yoanbernabeu/tap/grepai
```
### Linux/macOS (Alternative)
```bash
curl -sSL https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.sh | sh
```
### Windows
```powershell
irm https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.ps1 | iex
```
Verify: `grepai version`
## Step 2: Install Ollama (Local Embeddings)
### macOS
```bash
brew install ollama
ollama serve &
ollama pull nomic-embed-text
```
### Linux
```bash
curl -fsSL https://ollama.com/install.sh | sh
ollama serve &
ollama pull nomic-embed-text
```
Verify: `curl http://localhost:11434/api/tags`
## Step 3: Initialize Your Project
Navigate to your project and initialize GrepAI:
```bash
cd /path/to/your/project
grepai init
```
This creates `.grepai/config.yaml` with default settings:
- Ollama as embedding provider
- `nomic-embed-text` model
- GOB file storage
- Standard ignore patterns
## Step 4: Start Indexing
Start the watch daemon to index your code:
```bash
grepai watch
```
**What happens:**
1. Scans all source files (respects `.gitignore`)
2. Chunks code into ~512 token segments
3. Generates embeddings via Ollama
4. Stores vectors in `.grepai/index.gob`
**First indexing output:**
```
๐ GrepAI Watch
Scanning files...
Found 245 files
Processing chunks...
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ 100%
Indexed 1,234 chunks
Watching for changes...
```
### Background Mode
For long-running projects:
```bash
# Start in background
grepai watch --background
# Check status
grepai watch --status
# Stop when done
grepai watch --stop
```
## Step 5: Search Your Code
Now search semantically:
```bash
# Basic search
grepai search "authentication flow"
# Limit results
grepai search "error handling" --limit 5
# JSON output for scripts
grepai search "database queries" --json
```
### Example Output
```
Score: 0.89 | src/auth/middleware.go:15-45
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
func AuthMiddleware() gin.HandlerFunc {
return func(c *gin.Context) {
token := c.GetHeader("Authorization")
if token == "" {
c.AbortWithStatus(401)
return
}
// Validate JWT token...
}
}
Score: 0.82 | src/auth/jwt.go:23-55
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
func ValidateToken(tokenString string) (*Claims, error) {
token, err := jwt.Parse(tokenString, func(t *jwt.Token) (interface{}, error) {
return []byte(secretKey), nil
})
// ...
}
```
## Step 6: Analyze Call Graphs (Optional)
Trace function relationships:
```bash
# Who calls this function?
grepai trace callers "Login"
# What does this function call?
grepai trace callees "ProcessPayment"
# Full dependency graph
grepai trace graph "ValidateToken" --depth 3
```
## Complete Workflow Summary
```bash
# 1. Install (once)
brew install yoanbernabeu/tap/grepai
brew install ollama && ollama serve & && ollama pull nomic-embed-text
# 2. Setup project (once per project)
cd /your/project
grepai init
# 3. Index (run in background)
grepai watch --background
# 4. Search (as needed)
grepai search "your query here"
# 5. Trace (as needed)
grepai trace callers "FunctionName"
```
## Quick Command Reference
| Command | Purpose |
|---------|---------|
| `grepai init` | Initialize project config |
| `grepai watch` | Start indexing daemon |
| `grepai watch --background` | Run daemon in background |
| `grepai watch --status` | Check daemon status |
| `grepai watch --stop` | Stop daemon |
| `grepai search "query"` | Semantic search |
| `grepai search --json` | JSON output |
| `grepai trace callers "fn"` | Find callers |
| `grepai trace callees "fn"` | Find callees |
| `grepai status` | Index statistics |
| `grepai version` | Show version |
## Search Tips
**Be descriptive, not literal:**
- โ
"user authentication and session management"
- โ "auth"
**Describe intent:**
- โ
"where errors are logged to the console"
- โ "console.error"
**Use English:**
- Models are trained primarily on English text
- Works best with English queries
## Next Steps
After mastering the basics:
1. **Configure embeddings:** See `grepai-embeddings-*` skills
2. **Setup storage:** See `grepai-storage-*` skills
3. **Advanced search:** See `grepai-search-*` skills
4. **MCP integration:** See `grepai-mcp-*` skills
## Output Format
Successful quickstart:
```
โ
GrepAI Quickstart Complete
Project: /path/to/your/project
Files indexed: 245
Chunks created: 1,234
Embedder: Ollama (nomic-embed-text)
Storage: GOB (local file)
Try these searches:
- grepai search "main entry point"
- grepai search "database connection"
- grepai search "error handling"
```
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.