grepai-init

This skill covers the grepai init command and project initialization. Running grepai init creates the .grepai/ directory with: The generated config.yaml : Default patterns exclude: Edit .grepai/config.yaml to customize: For monorepos, init at the root: Or use workspaces for separate indices: If you need to reset: Warning: This deletes your index. You'll need to re-run grepai watch . After init, verify with: ❌ Problem: .grepai already exists ✅ Solution: Delete it first or edit existing config: ❌ Problem: Config created but Ollama not running ✅ Solution: Start Ollama before running grepai watch : ❌ Problem: Wrong directory initialized ✅ Solution: Remove .grepai and init in correct directory After successful initialization: - Setting up GrepAI in a new project - Understanding what grepai init creates - Customizing initial configuration - Troubleshooting initialization issues - Version control: .git - GrepAI data: .grepai - Dependencies: node_modules , vendor - Build outputs: target , dist , build - Cache: __pycache__ - Init at project root: Where your main code lives - Add .grepai/ to .gitignore : Index is machine-specific - Customize ignore patterns: Exclude generated/vendored code - Review config after init: Adjust for your stack