code-search
Skill1 starsChanged 8 months agoMITView on GitHub
Fast codebase search combining glob file matching and ripgrep content search. Find files by pattern, search code by regex, explore project structure. Use when needing to find files, search for patterns in code, understand codebase structure, or explore unfamiliar projects. Triggers on "find files", "search code", "grep for", "where is", "find all uses of", "explore this codebase", "project structure".
8 other projects use a version of this.
Adopted by
Most recently taken up by
- langwatch/langwatchtheir own version, first seen Oct 17, 2026
- elastic/sourcerertheir own version, first seen Oct 13, 2026
- gitextensions/gitextensionstheir own version, first seen Oct 8, 2026
- jmylchreest/aidetheir own version, first seen Aug 21, 2026
- Jinbae10/skillstheir own version, first seen Jul 7, 2026
- sumisingh10/qgrep-mcptheir own version, first seen Mar 31, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- gitextensions/gitextensions★ 8.6ksame name
- langwatch/langwatch★ 5ksame name
- kunwl123456/zeroclaw-skills-collection★ 27same name
- elastic/sourcerer★ 20same name
- jmylchreest/aide★ 19same name
- sumisingh10/qgrep-mcp★ 8same name
- brettatoms/agent-skills★ 3same name
- Jinbae10/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- code-navigateSkill
- code-simplifySkill
- magic-docsSkill
- memory-extractSkill
- memory-organizerSkill
- session-summarySkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 49
Use rg -F "literal" for exact strings with special chars
- Very specific: line 50
Use rg -l first (files only), then rg -n -C 2 for detail
“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Code Search — Fast Codebase Exploration
Efficient file and content search. Always prefer rg over raw grep.
File Search
find <dir> -type f -name "*.ts" | head -50 # by extension
find <dir> -type f -name "*.ts" -mtime -7 | head -30 # recently modified
find <dir> -path "*/services/*.ts" -type f # by path patternContent Search (ripgrep)
rg -l "pattern" <dir> # file list only
rg -n -C 2 "pattern" <dir> # with context
rg -n "pattern" --type ts <dir> # filter by type
rg -n "TODO" -g "*.ts" -g "!node_modules" <dir> # glob filter
rg -c "pattern" <dir> # count per file
rg -n -U "interface\s*\{[^}]*\}" <dir> --type ts # multilineProject Structure Discovery
find <dir> -maxdepth 2 -type d | sort | head -50find <dir> -maxdepth 2 \( -name "package.json" -o -name "tsconfig.json" -o -name "Makefile" -o -name "*.toml" \) | sortrg -l "main\(|export default|app\." <dir> --type ts --type js | head -20find <dir> -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn | head -15
Common Patterns
| Task | Command |
| Where is X defined? | rg -n "(?:function|class|const|type|interface)\s+X" <dir> --type ts |
| What calls X? | rg -n "X\(" <dir> --type ts -g "!*.test.*" |
| What changed recently? | git log --oneline -20 / git diff --stat HEAD~5 |
| API surface | rg -n "export\s+(function|class|const|type)" <dir>/src --type ts | head -40 |
Tips
- Exclude
node_modules,.git,dist,build: use-g "!node_modules" - Pipe through
head -Nto avoid flooding context - Use
rg -F "literal"for exact strings with special chars - Use
rg -lfirst (files only), thenrg -n -C 2for detail - Fallback:
grep -rn --include="*.ts"ifrgunavailable
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

