domains / families / software-engineering / file-search

file-search

combined

Fast file-name and content search using `fd` and `rg` (ripgrep). Perform fast file name and content searches with ripgrep (rg); use it when you need to locate files by glob/regex, find keywords across directories, or replace common find/grep workflows.

When to use

• You need to list files matching a pattern (e.g., `*.rs`, `*.md`) across a project quickly.
• You want to find occurrences of a keyword/regex (e.g., `TODO|FIXME`) across one or more directories.
• You need contextual matches (lines before/after) to understand how a symbol or string is used.
• You want a faster, simpler replacement for typical `find` + `grep` pipelines.
• You need to narrow searches by file type (e.g., Rust-only) while scanning large repositories.

When not to use

• Do not use this skill when the required source data, identifiers, files, or credentials are missing.
• Do not use this skill when the user asks for fabricated results, unsupported claims, or out-of-scope conclusions.
• Do not use this skill when a simpler direct answer is more appropriate than the documented workflow.

Skill page

Conflict

The two skills cover the same core task (fast file search) but rely on different primary tools and workflows. The first skill (LeoYeAI) uses `fd` for filename search and `rg` for content search, while the second skill (aipoch) uses `rg --files` for both filename and content search. The second skill also includes extensive boilerplate for validation, safety, and output contracts that the first lacks. Because the first skill provides a distinct and often preferred tool (`fd`) for filename operations that the second omits, and the second provides a self-contained `rg`-only workflow, crowning one would hide a valid alternative approach. They are complementary rather than one being a strict reproduction of the other.