
Grepai Ignore Patterns
Tune which paths GrepAI indexes so semantic code search stays fast and relevant in solo repos.
Install
npx skills add https://github.com/yoanbernabeu/grepai-skills --skill grepai-ignore-patternsWhat is this skill?
- 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
Adoption & trust: 478 installs on skills.sh; 17 GitHub stars; 3/3 security scanners passed (skills.sh audits); trending (+100% hot-view momentum).
Recommended Skills
Microsoft Foundrymicrosoft/azure-skills
Azure Aimicrosoft/azure-skills
Azure Hosted Copilot Sdkmicrosoft/azure-skills
Lark Eventlarksuite/cli
Running Claude Code Via Litellm Copilotxixu-me/skills
Setup Matt Pocock Skillsmattpocock/skills
Journey fit
Primary fit
Ignore-pattern setup happens while wiring AI search and agent tooling into the codebase during the build phase. GrepAI indexing is agent-adjacent developer tooling, so agent-tooling is the canonical shelf for configuration skills like this.
Common Questions / FAQ
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.
SKILL.md
READMESKILL.md - Grepai Ignore Patterns
# 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 ```yaml # .grepai/config.yaml ignore: - pattern1 - pattern2 ``` ## Pattern Syntax ### Directory Patterns ```yaml ignore: # Exact directory name (matches anywhere) - node_modules - vendor - __pycache__ # With trailing slash (explicit directory) - dist/ - build/ - coverage/ ``` ### File Patterns ```yaml ignore: # Exact filename - package-lock.json - yarn.lock # Wildcard patterns - "*.min.js" - "*.min.css" - "*.map" - "*.lock" ``` ### Path Patterns ```yaml ignore: # Paths containing substring - /tests/ - /spec/ - /__tests__/ # Specific paths - src/generated/ - api/swagger/ ``` ### Glob Patterns ```yaml ignore: # Double star (recursive) - "**/test/**" - "**/mock/**" # Single star (single level) - "*.test.js" - "*.spec.ts" - "*_test.go" ``` ## Default Ignore Patterns GrepAI's default configuration includes: ```yaml 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 - .output ``` ## Common Ignore Configurations ### JavaScript/TypeScript Project ```yaml ignore: - node_modules - dist - build - coverage - .nyc_output - "*.min.js" - "*.bundle.js" - "*.map" - package-lock.json - yarn.lock - pnpm-lock.yaml ``` ### Go Project ```yaml ignore: - vendor - bin - "*.pb.go" # Protobuf generated - "*_mock.go" # Mocks - "mocks/" - go.sum ``` ### Python Project ```yaml ignore: - __pycache__ - .pytest_cache - .mypy_cache - .venv - venv - env - "*.pyc" - "*.pyo" - .eggs - "*.egg-info" - dist - build ``` ### Rust Project ```yaml ignore: - target - Cargo.lock - "*.rlib" ``` ### Java/Kotlin Project ```yaml ignore: - target - build - .gradle - "*.class" - "*.jar" - "*.war" ``` ### Monorepo ```yaml 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: ```yaml 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: ```yaml search: boost: penalties: - pattern: /tests/ factor: 0.5 - pattern: _test. factor: 0.5 ``` ## Excluding Generated Code ```yaml ignore: # Generated markers - "**/generated/**" - "*.generated.*" - "*.gen.*" # Specific generators - "*.pb.go" # Protobuf - "*.graphql.ts" # GraphQL codegen - "*.d.ts" # TypeScript declarations - "swagger_*.go" # Swagger - "openapi_*.ts" # OpenAPI ``` ## Excluding Documentation ```yaml ignore: - docs/ - documentation/ - "*.md" - "*.mdx" - "*.rst" ``` ## Verifying Ignore Patterns Check what's being indexed: