ripgrep-patterns

name	ripgrep-patterns
description	Fast codebase search and file discovery with ripgrep (`rg`). Use when finding symbols, text patterns, TODOs, config keys, or candidate files before implementation.
allowed-tools	Read, Grep, Glob, Bash

ripgrep Patterns

Use this skill when the task requires fast search, code discovery, or targeted filtering in large repos.

Core Rules

1. Prefer rg over grep for speed and better defaults.
2. Start broad, then narrow with globs, file types, and line numbers.
3. Use --files for file discovery, -n for line references, and -C for quick context.
4. Ignore generated or vendor directories unless explicitly needed.
5. Use fixed-string mode (-F) when regex is unnecessary.

High-Value Commands

# Text search with line numbers
rg -n "pattern" .

# Case-insensitive search
rg -n -i "pattern" .

# Fixed-string search (faster, safer for special chars)
rg -n -F "literal_text" .

# Search only specific file types
rg -n "useEffect\\(" -t ts -t tsx .

# Include hidden files but keep .git ignored
rg -n "pattern" --hidden .

# Exclude noisy paths
rg -n "pattern" . -g '!node_modules' -g '!.next' -g '!dist'

# Find files by name patterns quickly
rg --files -g '**/*.{ts,tsx,js,jsx}'

# Show context around matches
rg -n -C 2 "pattern" .

Practical Workflow

1. Discover candidates: rg --files -g '**/*.{ts,tsx,js,jsx,json,md}'
2. Locate behavior: rg -n "keyword_or_symbol" .
3. Narrow surface area: add -g filters, file types, or target subpaths.
4. Confirm exact edits: rerun with -n -C 2 before editing.

Safety and Quality

• Never run destructive commands from search results.
• Treat matches as hints, not truth. Always open files and verify context.
• For refactors, run search before and after changes to confirm coverage.
• Prefer deterministic queries in commit/review notes.

For additional command recipes, see references/command-recipes.md.