
grepai-installation
Multi-platform installation guide for GrepAI. Use this skill when installing GrepAI on macOS, Linux, or Windows.
- Installs
- 591
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-installation- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads grepai-installation automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
GrepAI Installation
This skill covers all methods to install GrepAI on any platform.
When to Use This Skill
- Installing GrepAI for the first time
- Upgrading an existing GrepAI installation
- Building GrepAI from source
- Verifying a successful installation
Prerequisites
- macOS/Linux: Terminal access
- Windows: PowerShell
- From source: Go 1.24+ installed
Installation Methods
Method 1: Homebrew (macOS - Recommended)
The easiest way to install on macOS:
# Add the tap and install
brew install yoanbernabeu/tap/grepai
# Verify installation
grepai version
Advantages:
- Automatic updates with
brew upgrade grepai - Clean uninstall with
brew uninstall grepai - Manages dependencies automatically
Method 2: Shell Script (Linux/macOS)
Universal installation script:
# Download and run the installer
curl -sSL https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.sh | sh
# Verify installation
grepai version
What the script does:
- Detects your OS and architecture
- Downloads the appropriate binary
- Installs to
/usr/local/bin/ - Sets executable permissions
Method 3: PowerShell (Windows)
Native Windows installation:
# Run in PowerShell (Admin recommended)
irm https://raw.githubusercontent.com/yoanbernabeu/grepai/main/install.ps1 | iex
# Verify installation
grepai version
Note: You may need to adjust execution policy:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
Method 4: Build from Source
For developers or custom builds:
# Clone the repository
git clone https://github.com/yoanbernabeu/grepai.git
cd grepai
# Build the binary
make build
# Install globally
sudo mv ./bin/grepai /usr/local/bin/
# Verify installation
grepai version
Requirements:
- Go 1.24 or later
- Make (optional, can use
go builddirectly)
Verifying Installation
After installation, verify everything works:
# Check version
grepai version
# Output: grepai version 0.24.0
# Check available commands
grepai --help
Updating GrepAI
Check for Updates
grepai update --check
Perform Update
# Auto-update (downloads and installs latest)
grepai update
# Or via Homebrew
brew upgrade grepai
Uninstalling
Homebrew
brew uninstall grepai
Manual
# Remove binary
sudo rm /usr/local/bin/grepai
# Optionally remove config directories
rm -rf ~/.grepai
Next Steps
After installation:
- Install Ollama for local embeddings (see
grepai-ollama-setupskill) - Initialize a project with
grepai init - Start indexing with
grepai watch
Common Installation Issues
❌ Problem: command not found: grepai
✅ Solution: Ensure /usr/local/bin is in your PATH:
export PATH="$PATH:/usr/local/bin"
❌ Problem: Permission denied during installation
✅ Solution: Use sudo for the installation command or install to a user directory
❌ Problem: Homebrew tap not found ✅ Solution: Add the tap first:
brew tap yoanbernabeu/tap
brew install grepai
Output Format
After successful installation:
✅ GrepAI installed successfully
Version: 0.24.0
Location: /usr/local/bin/grepai
Next steps:
1. Install Ollama: brew install ollama
2. Initialize project: grepai init
3. Start indexing: grepai watch
FAQ
What does the grepai-installation skill do?
Multi-platform installation guide for GrepAI. Use this skill when installing GrepAI on macOS, Linux, or Windows.
How do I install grepai-installation?
Run npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-installation in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/grepai-installation/ (personal) or .claude/skills/grepai-installation/ (project).
Which AI agents can use grepai-installation?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is grepai-installation safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains grepai-installation?
It is published by yoanbernabeu in yoanbernabeu/grepai-skills. It has 591 recorded installs.
More from yoanbernabeu/grepai-skills
grepai-search-basics
yoanbernabeu/grepai-skills
Basic semantic code search with GrepAI. Use this skill to learn fundamental search commands and concepts.
grepai-search-advanced
yoanbernabeu/grepai-skills
Advanced search options in GrepAI. Use this skill for JSON output, compact mode, and AI agent integration.
grepai-trace-graph
yoanbernabeu/grepai-skills
Build complete call graphs with GrepAI trace. Use this skill for recursive dependency analysis.
grepai-ollama-setup
yoanbernabeu/grepai-skills
Install and configure Ollama for local embeddings with GrepAI. Use this skill when setting up private, local embedding generation.
grepai-trace-callers
yoanbernabeu/grepai-skills
Find function callers with GrepAI trace. Use this skill to discover what code calls a specific function.
grepai-search-tips
yoanbernabeu/grepai-skills
Tips and best practices for effective GrepAI searches. Use this skill to improve search result quality.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.