find

Find Files Command

Find files matching: $ARGUMENTS

Instructions

Use code_file_search to find files by pattern.

Usage

code_file_search({
  pattern: "$ARGUMENTS",
  repo: "<repo>"  // one of the project's repos (project.json → repos); adjust based on context
})

Examples

• *Order*.tsx - Find all files with "Order" in the name
• *.spec.ts - Find all test files
• *.sql - Find all SQL migration files
• *Service*.ts - Find all service files
• values*.yaml - Find deploy/values files

Repositories

If the user doesn't specify a repo, pick the most likely one from the project's .claude/project.json (repos, mainApp, device) based on the file pattern — e.g. web extensions (.tsx, route.ts) map to the mainApp; .py/firmware patterns map to the device repo if one is defined; deploy manifests map to the infrastructure repo. The layout varies per project, so read it — don't assume.

Fallback

If MCP tools are not available:

WebFetch({ url: "http://localhost:4001/search/files?pattern=PATTERN&repo=<codePath>/<repo>" })

(codePath from project.json.)

---

Now find files matching: $ARGUMENTS

How to use

What it does

Finds files by name pattern across every repository in your project. You give it a glob like *Service*.ts, and it searches the right repo for you — picking the most likely one from your project configuration when you don't name it. You get back a list of matching file paths instead of guessing where something lives.

When to use it

• You know part of a filename but not which repo or directory holds it.
• You want every file of a kind at once — all test specs, all SQL migrations, all deploy value files.
• You are new to a project and need to see how files of a given type are laid out.
• You are about to edit a component and want to confirm there is only one file with that name.

When not to use it

• You are searching for text inside files, not filenames — use /search instead.
• You want to know what breaks if you change a file — use /impact for that.
• You already know the exact path; just read the file directly.