This skill covers how to configure ignore patterns to exclude files and directories from GrepAI indexing.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongrepai-ignore-patternsExecute the skills CLI command in your project's root directory to begin installation:
Fetches grepai-ignore-patterns from yoanbernabeu/grepai-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate grepai-ignore-patterns. Access via /grepai-ignore-patterns in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
16
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
16
stars
This skill covers how to configure ignore patterns to exclude files and directories from GrepAI indexing.
GrepAI uses two sources for ignore patterns:
.grepai/config.yaml - Custom patterns you define.gitignore - Automatically respected# .grepai/config.yaml
ignore:
- pattern1
- pattern2
ignore:
# Exact directory name (matches anywhere)
- node_modules
- vendor
- __pycache__
# With trailing slash (explicit directory)
- dist/
- build/
- coverage/
ignore:
# Exact filename
- package-lock.json
- yarn.lock
# Wildcard patterns
- "*.min.js"
- "*.min.css"
- "*.map"
- "*.lock"
ignore:
# Paths containing substring
- /tests/
- /spec/
- /__tests__/
# Specific paths
- src/generated/
- api/swagger/
ignore:
# Double star (recursive)
- "**/test/**"
- "**/mock/**"
# Single star (single level)
- "*.test.js"
- "*.spec.ts"
- "*_test.go"
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
- .output
ignore:
- node_modules
- dist
- build
- coverage
- .nyc_output
- "*.min.js"
- "*.bundle.js"
- "*.map"
- package-lock.json
- yarn.lock
- pnpm-lock.yaml
ignore:
- vendor
- bin
- "*.pb.go" # Protobuf generated
- "*_mock.go" # Mocks
- "mocks/"
- go.sum
ignore:
- __pycache__
- .pytest_cache
- .mypy_cache
- .venv
- venv
- env
- "*.pyc"
- "*.pyo"
- .eggs
- "*.egg-info"
- dist
- build
ignore:
- target
- Cargo.lock
- "*.rlib"
ignore:
- target
- build
- .gradle
- "*.class"
- "*.jar"
- "*.war"
ignore:
# Common
- node_modules
- dist
- build
- coverage
# Specific packages to exclude
- packages/legacy/
- packages/deprecated/
# Generated
- "**/generated/**"
- "**/__generated__/**"
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.5
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
ignore:
- docs/
- documentation/
- "*.md"
- "*.mdx"
- "*.rst"
Check what's being indexed:
# Check index status
grepai status
# Output shows file count
# If too high, add more ignore patterns
❌ 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
node_modules, vendor, etc.dist, build, target"*.min.js" not *.min.jsAfter modifying ignore patterns:
# Stop existing daemon
grepai watch --stop
# Clear index and restart
rm .grepai/index.gob
grepai watch
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.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
giuseppe-trisciuoglio/developer-kit
giuseppe-trisciuoglio/developer-kit
wshobson/agents
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
Useful defaults in grepai-ignore-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for grepai-ignore-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
grepai-ignore-patterns is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for grepai-ignore-patterns matched our evaluation — installs cleanly and behaves as described in the markdown.
grepai-ignore-patterns fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
grepai-ignore-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added grepai-ignore-patterns from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
grepai-ignore-patterns is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
grepai-ignore-patterns reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in grepai-ignore-patterns — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 68