code-search-tool
Skill0 starsChanged 32 days agoMIT-0View on GitHub
Search file contents with the built-in code_search tool (ripgrep, or grep when rg is missing) to find definitions, usages, strings and patterns across a codebase or folder.
In this repository34 other files it gives its agents.
- autoresearchSkill
- browser-toolSkill
- claude-codeSkill
- codex-cliSkill
- coding-agentSkill
- docxSkill
- electronSkill
- exec-toolSkill
- gemini-cliSkill
- geminiSkill
- githubSkill
- git-toolSkill
- gwsSkill
- healthcheckSkill
- himalayaSkill
- notionSkill
- obsidianSkill
- outlookSkill
- outlook-webSkill
- pdfSkill
- pptxSkill
- quipSkill
- research-assistantSkill
- sherpa-onnx-ttsSkill
- skill-creatorSkill
- sonosSkill
- spotify-playerSkill
- spotifySkill
- tmuxSkill
- video-framesSkill
- voice-callSkill
- weatherSkill
- web-fetch-toolSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
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 27
Use context: 0 and a narrow filePattern when you only need file and line numbers.
- Very specific: line 28
When results are truncated, narrow path or filePattern before raising maxResults.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
code_search
| Parameter | Meaning |
pattern | Regular expression (ripgrep syntax when rg is installed, grep syntax otherwise). |
path | Directory to search: absolute, ~/..., or relative to the workspace folder (the default). |
filePattern | File glob, for example *.ts or *.py. |
ignoreCase | Case-insensitive match. Default false. |
context | Lines of context around each match. Default 2. |
maxResults | Match cap. Default 50. truncated: true in the result means there were more. |
Tips
- Point
pathat a repository or subfolder; searching the home folder is slow and noisy. - Find a definition with an anchored pattern, for example
function parseConfig|const parseConfig =or^class Foo. - Escape regex characters you mean literally (
\.,\(). - Use
context: 0and a narrowfilePatternwhen you only need file and line numbers. - When results are truncated, narrow
pathorfilePatternbefore raisingmaxResults. - Then read the hit with
file_read(it takes an offset and limit) instead of re-searching. - To list files by name rather than content, use
execwithrg --files -g '<glob>'orfind.
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.

