
Grepai Ignore Patterns
- 567 installs
- 18 repo stars
- Updated February 1, 2026
- yoanbernabeu/grepai-skills
grepai-ignore-patterns is an agent skill that configures GrepAI ignore patterns in .grepai/config.yaml for developers who need faster, more relevant semantic code search by excluding vendored and generated files.
About
grepai-ignore-patterns is a configuration skill from yoanbernabeu/grepai-skills for controlling which paths GrepAI indexes. Ignore rules come from .grepai/config.yaml and are automatically merged with .gitignore patterns. Developers use grepai-ignore-patterns when excluding test files, generated code, vendor directories like node_modules, or other noise that bloats the index and dilutes search results. Pattern syntax supports exact directory names such as node_modules and vendor anywhere in the tree. Reach for this skill after initial grepai watch setup when search quality or index size needs tuning.
- Documents ignore rules in `.grepai/config.yaml` with a clear YAML shape
- Automatically respects `.gitignore` alongside custom ignore entries
- Covers directory, file, path substring, and glob patterns including `**` recursion
- Shows how to drop tests, generated code, vendor trees, and lockfiles from the index
- Explains when to exclude artifacts to shrink index size and clean search hits
Grepai Ignore Patterns by the numbers
- 567 all-time installs (skills.sh)
- +4 installs in the week ending Jul 28, 2026 (Skillselion tracking)
- Ranked #1,638 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Jul 28, 2026 (Skillselion catalog sync)
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-ignore-patternsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 567 |
|---|---|
| repo stars | ★ 18 |
| Security audit | 3 / 3 scanners passed |
| Last updated | February 1, 2026 |
| Repository | yoanbernabeu/grepai-skills ↗ |
How do you exclude files from GrepAI indexing?
Tune which paths GrepAI indexes so semantic code search stays fast and relevant in repos.
Who is it for?
Teams running GrepAI who need smaller indexes and cleaner semantic search by excluding tests, vendor, or generated code.
Skip if: First-time GrepAI MCP setup before any index exists—use grepai-mcp-claude or core GrepAI install docs instead.
When should I use this skill?
The user wants to exclude directories from GrepAI, reduce index size, or stop test or vendor files appearing in semantic search.
What you get
Updated .grepai/config.yaml ignore list respecting .gitignore plus custom directory and path exclusions.
- .grepai/config.yaml ignore rules
- tuned semantic search index scope
Files
GrepAI Ignore Patterns
This skill covers how to configure ignore patterns to exclude files and directories from GrepAI indexing.
When to Use This Skill
- Excluding test files from search results
- Ignoring generated or vendored code
- Reducing index size by excluding unnecessary files
- Customizing which files GrepAI indexes
How Ignore Patterns Work
GrepAI uses two sources for ignore patterns:
1. `.grepai/config.yaml` - Custom patterns you define 2. `.gitignore` - Automatically respected
Configuration Location
# .grepai/config.yaml
ignore:
- pattern1
- pattern2Pattern Syntax
Directory Patterns
ignore:
# Exact directory name (matches anywhere)
- node_modules
- vendor
- __pycache__
# With trailing slash (explicit directory)
- dist/
- build/
- coverage/File Patterns
ignore:
# Exact filename
- package-lock.json
- yarn.lock
# Wildcard patterns
- "*.min.js"
- "*.min.css"
- "*.map"
- "*.lock"Path Patterns
ignore:
# Paths containing substring
- /tests/
- /spec/
- /__tests__/
# Specific paths
- src/generated/
- api/swagger/Glob Patterns
ignore:
# Double star (recursive)
- "**/test/**"
- "**/mock/**"
# Single star (single level)
- "*.test.js"
- "*.spec.ts"
- "*_test.go"Default Ignore Patterns
GrepAI's default configuration includes:
ignore:
# Version control
- .git
- .svn
- .hg
# GrepAI itself
- .grepai
# Package managers
- node_modules
- vendor
- .npm
- .yarn
# Build outputs
- target
- dist
- build
- out
# Cache directories
- __pycache__
- .pytest_cache
- .mypy_cache
- .cache
# Framework outputs
- .next
- .nuxt
- .outputCommon Ignore Configurations
JavaScript/TypeScript Project
ignore:
- node_modules
- dist
- build
- coverage
- .nyc_output
- "*.min.js"
- "*.bundle.js"
- "*.map"
- package-lock.json
- yarn.lock
- pnpm-lock.yamlGo Project
ignore:
- vendor
- bin
- "*.pb.go" # Protobuf generated
- "*_mock.go" # Mocks
- "mocks/"
- go.sumPython Project
ignore:
- __pycache__
- .pytest_cache
- .mypy_cache
- .venv
- venv
- env
- "*.pyc"
- "*.pyo"
- .eggs
- "*.egg-info"
- dist
- buildRust Project
ignore:
- target
- Cargo.lock
- "*.rlib"Java/Kotlin Project
ignore:
- target
- build
- .gradle
- "*.class"
- "*.jar"
- "*.war"Monorepo
ignore:
# Common
- node_modules
- dist
- build
- coverage
# Specific packages to exclude
- packages/legacy/
- packages/deprecated/
# Generated
- "**/generated/**"
- "**/__generated__/**"Excluding Test Files
To focus search on production code:
ignore:
# Test directories
- tests/
- test/
- __tests__/
- spec/
# Test files by pattern
- "*.test.js"
- "*.test.ts"
- "*.spec.js"
- "*.spec.ts"
- "*_test.go"
- "test_*.py"
- "*_test.py"Alternative: Use search boosting instead to penalize (not exclude) tests:
search:
boost:
penalties:
- pattern: /tests/
factor: 0.5
- pattern: _test.
factor: 0.5Excluding Generated Code
ignore:
# Generated markers
- "**/generated/**"
- "*.generated.*"
- "*.gen.*"
# Specific generators
- "*.pb.go" # Protobuf
- "*.graphql.ts" # GraphQL codegen
- "*.d.ts" # TypeScript declarations
- "swagger_*.go" # Swagger
- "openapi_*.ts" # OpenAPIExcluding Documentation
ignore:
- docs/
- documentation/
- "*.md"
- "*.mdx"
- "*.rst"Verifying Ignore Patterns
Check what's being indexed:
# Check index status
grepai status
# Output shows file count
# If too high, add more ignore patternsCommon Issues
❌ Problem: Index is too large ✅ Solution: Add more ignore patterns for dependencies and generated files
❌ Problem: Search returns vendor/test code ✅ Solution: Either ignore or use boosting penalties
❌ Problem: Pattern not working ✅ Solution: Check syntax - use quotes for patterns with special characters:
ignore:
- "*.min.js" # Correct
- *.min.js # May cause YAML parsing issues❌ Problem: Need to include previously ignored files ✅ Solution: Remove from ignore list and re-run grepai watch
Best Practices
1. Start with defaults: Add patterns as needed 2. Exclude dependencies: Always ignore node_modules, vendor, etc. 3. Exclude build outputs: dist, build, target 4. Exclude lock files: Large, not useful for search 5. Consider boosting vs ignoring: Penalize instead of exclude for test files 6. Quote special characters: "*.min.js" not *.min.js
Re-indexing After Changes
After modifying ignore patterns:
# Stop existing daemon
grepai watch --stop
# Clear index and restart
rm .grepai/index.gob
grepai watchOutput Format
After configuring ignore patterns:
✅ Ignore Patterns Configured
Patterns: 15 configured
Categories:
- Directories: node_modules, vendor, dist, build
- File types: *.min.js, *.map, *.lock
- Paths: /tests/, /docs/
Also respecting: .gitignore
Run 'grepai watch' to re-index with new patterns.Related skills
FAQ
Where are GrepAI ignore patterns configured?
GrepAI ignore patterns are configured in .grepai/config.yaml under an ignore list. GrepAI also automatically respects .gitignore, so custom patterns in config.yaml add exclusions beyond gitignored paths.
Why use grepai-ignore-patterns?
Use grepai-ignore-patterns to exclude test files, generated code, vendor directories, and other noise from indexing. Smaller, focused indexes improve semantic search speed and result relevance in GrepAI.
Is Grepai Ignore Patterns safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.