file-search

Included with Lifetime

$97 forever

Fast file and text search across the codebase. Use when you need to find files by name, search code by content, locate definitions, find usages/imports, or explore project structure. Triggers on "find file", "search for", "where is", "grep for", "locate", "find definition", "find usage", "search codebase", "find all references".

Writing & Docs

What this skill does


<objective>
Execute fast, thorough file and text searches across the codebase using a lightweight haiku agent. Returns precise results with file paths, line numbers, and context — never modifies files.
</objective>

<search_modes>
This skill handles all search types automatically based on input:

| Input Pattern | Search Mode | What Happens |
|--------------|-------------|--------------|
| File name or glob pattern | **File search** | Finds files by name/pattern across the project |
| Text string or regex | **Content search** | Greps file contents for matches |
| Function/class/type name | **Definition search** | Finds where something is defined + its signature |
| "usages of X" / "who calls X" | **Usage search** | Finds all imports and call sites |
| "imports of X" | **Import search** | Finds all files that import a module |
| Directory path or "structure" | **Structure exploration** | Maps directory layout and key files |
| "related to X" | **Related files** | Finds dependencies and dependents of a file |

The agent runs multiple search strategies in parallel and cross-references results for completeness.
</search_modes>

<tips>
- Be specific: "find where UserService is defined" beats "find UserService"
- Include file type hints: "find login handler in Python files"
- Use quotes for exact phrases: search for "database connection pool"
- Scope by directory: "search for auth middleware in src/api/"
- Chain searches: "find all files that import from utils/auth"
</tips>

<success_criteria>
- Returns file paths with line numbers for all matches
- Exhausts multiple search strategies before reporting "not found"
- Results are ordered by relevance
- No false positives — every result was verified by a tool call
</success_criteria>

Files: 1

Size: 2.2 KB

Complexity: 12/100

Category: Writing & Docs

Source: https://github.com/cfircoo/claude-code-toolkit/tree/main/skills/file-search

Related in Writing & Docs

jax-development

Included

Use this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.

Writing & Docsscripts

nature-article-writer

Included

Drafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.

Writing & Docsscripts

deckrd

Included

Document-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.

Writing & Docsscripts

clinical-decision-support

Included

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

Writing & Docsscripts

handling-sf-data

Included

Salesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).

Writing & Docsscripts

accelint-ac-to-playwright

Included

Convert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.

Writing & Docsscripts