菜单
Search a codebase efficiently with ripgrep regular expressions, file globs, and git history search. Use to locate symbols, usages, and definitions instead of reading whole files.
| name | code-search |
| description | Search a codebase efficiently with ripgrep regular expressions, file globs, and git history search. Use to locate symbols, usages, and definitions instead of reading whole files. |
The built-in grep tool matches LITERAL text only. For real regular-expression search and
history-aware lookups, drive ripgrep and git through execute.
rg -n "fn\s+\w+\(" src/, rg -n --type java "class \w+Service".rg -n "\bmyFunction\b".rg -n --type ts "useEffect\(".rg -l "TODO"; find files by name: rg --files | rg <name> or use glob.git log -S "<string>" --oneline.git blame -L <start>,<end> <file>.git grep -n "<regex>".-F to ripgrep.Four-layer skill composition, skill marketplaces, the self-learning loop
四层技能合成、技能市场、自学习闭环
Use when the user asks for a summary, TL;DR, or condensed version of any content.
Apply multi-file or tricky edits atomically with git apply instead of many fragile edit_file calls. Use when changing several files at once or when edit_file fails to match.
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.