grepai-quickstart

yoanbernabeu/grepai-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-quickstart
0 commentsdiscussion
summary

This skill provides a complete walkthrough to get GrepAI running and searching your code in 5 minutes.

skill.md

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

brew install yoanbernabeu/tap/grepai

Linux/macOS (Alternative)

curl -sSL https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.sh | sh

Windows

irm https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.ps1 | iex

Verify: grepai version

Step 2: Install Ollama (Local Embeddings)

macOS

brew install ollama
ollama serve &
ollama pull nomic-embed-text

Linux

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:

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:

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:

# 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:

# 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:

# 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

# 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"
how to use grepai-quickstart

How to use grepai-quickstart on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add grepai-quickstart
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-quickstart

The skills CLI fetches grepai-quickstart from GitHub repository yoanbernabeu/grepai-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/grepai-quickstart

Reload or restart Cursor to activate grepai-quickstart. Access the skill through slash commands (e.g., /grepai-quickstart) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.730 reviews
  • Neel Desai· Dec 28, 2024

    grepai-quickstart is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Chaitanya Patil· Dec 8, 2024

    Solid pick for teams standardizing on skills: grepai-quickstart is focused, and the summary matches what you get after install.

  • Piyush G· Nov 27, 2024

    We added grepai-quickstart from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Rahul Santra· Nov 23, 2024

    I recommend grepai-quickstart for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Jin Bhatia· Nov 19, 2024

    grepai-quickstart reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Shikha Mishra· Oct 18, 2024

    grepai-quickstart fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Pratham Ware· Oct 14, 2024

    Useful defaults in grepai-quickstart — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Jin Reddy· Oct 10, 2024

    Registry listing for grepai-quickstart matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Lucas Malhotra· Sep 5, 2024

    grepai-quickstart is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Arya Farah· Aug 24, 2024

    Keeps context tight: grepai-quickstart is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 30

1 / 3