How do I search across a repository?

Run /eidetic:search with your semantic query and ensure PROJECT_PATH points to a git repo that is indexed.

What happens if the repository isn't indexed?

The system will prompt to index; run /eidetic:index or confirm to index, then perform the search.

How many results are shown and how can I customize?

The default limit is 10 results. You can adjust the limit in the search invocation or refine the query to narrow results.

search

Scanned

npx machina-cli add skill eidetics/claude-eidetic/search --openclaw

Files (1)

SKILL.md

984 B

/search

Usage: /eidetic:search <query>

Step 1: Parse Query

Use the argument as the query. If none, ask: "What would you like to search for?"

Step 2: Detect Path

git rev-parse --show-toplevel 2>/dev/null || echo "NO_GIT_REPO"

If NO_GIT_REPO, ask for the path. Store as PROJECT_PATH.

Step 3: Check Index

get_indexing_status(path="<PROJECT_PATH>")

If not indexed: "Run /eidetic:index first, or I can index now." If user agrees, run index_codebase(path="<PROJECT_PATH>") then continue.

Step 4: Search

search_code(path="<PROJECT_PATH>", query="<USER_QUERY>", limit=10)

Step 5: Present Results

## Search: "<query>" in <project>
1. `path/to/file.ts:42` — <snippet>
2. `path/to/other.ts:15` — <snippet>
**<N> results** | <file count> files indexed

If no results: suggest different terms, check index completeness, or use Grep for exact matches.

Source

git clone https://github.com/eidetics/claude-eidetic/blob/main/plugin/plugins/claude-eidetic/skills/search/SKILL.mdView on GitHub

Overview

This skill enables semantic code search across a codebase using Eidetic. It detects the project path, checks if the repository is indexed, and runs a semantic query to return file paths with code snippets. If the repo isn’t indexed yet, it guides you to index before searching.

How This Skill Works

You invoke the search with /eidetic:search followed by your query. The system determines PROJECT_PATH, checks the indexing status via get_indexing_status, and may index the codebase using index_codebase if needed. It then runs search_code with path, query, and a limit, and presents results as file:line and snippet.

When to Use It

You need to locate a function or semantic concept across a codebase without relying on exact string matches.
You just cloned a repository and want to quickly find where a feature is implemented.
You are refactoring and need to locate all usages of a symbol across files.
You want to understand how a utility is used in different parts of the project.
The index is missing or incomplete and you want to determine if you should index before searching.

Quick Start

Step 1: Run /eidetic:search <query> to start a semantic search.
Step 2: If you are not in a git repo, provide PROJECT_PATH or navigate to the repo root.
Step 3: If the project isn’t indexed, run /eidetic:index to index, then re-run the search.

Best Practices

Ensure you are in a Git repository or provide a valid PROJECT_PATH.
Index the codebase before searching if the index is missing or out of date.
Use semantic queries that describe intent (functionality, behavior) rather than exact text.
Limit results to a manageable number (default is 10) to keep findings actionable.
If no results appear, refine terms, verify index completeness, or try a grep for exact matches.

Example Use Cases

Search for a function named loadUser across a React project.
Find all usages of a debounce helper in the codebase.
Locate every reference to a configuration flag related to API mode.
Identify where a new security check is implemented across modules.
Track where a feature flag is evaluated in different files.

Frequently Asked Questions

Add this skill to your agents