---
name: Codebase Search
slug: codebase-search-2
category: Automation
description: Codebase Search guides a local-first workflow for understanding a repository before web lookup. Use it to check index status, then find symbols, dependencies, implementations, and similar code with semantic and graph tools.
github: "https://github.com/Helweg/open-codebase-index/tree/main/skills/codebase-search"
language: TypeScript
stars: 186
forks: 29
install: "npx degit https://github.com/Helweg/open-codebase-index/tree/main/skills/codebase-search ~/.claude/skills/codebase-search"
installs_to: ~/.claude/skills/codebase-search
source_path: skills/codebase-search/SKILL.md
collection_size: 2
category_size: 2032
collection_url: "https://dirskills.com/collections/Helweg/open-codebase-index"
added: 2026-09-06T05:20:26.556Z
last_synced: 2026-09-06T05:20:26.556Z
canonical_url: "https://dirskills.com/skills/codebase-search-2"
---

# Codebase Search

Codebase Search guides a local-first workflow for understanding a repository before web lookup. Use it to check index status, then find symbols, dependencies, implementations, and similar code with semantic and graph tools.

**Install:**

```bash
npx degit https://github.com/Helweg/open-codebase-index/tree/main/skills/codebase-search ~/.claude/skills/codebase-search
```

## README

# Codebase Search Skill

Use this skill when you need local repository knowledge before web lookup.

## Core workflow

1. Run `index_status` when index readiness or freshness is unknown.
2. Use `codebase_context(query, ...)` before shell search, grep, or broad file reads. Pass `symbol` for an authoritative definition or `from` + `to` for a dependency path.
3. Use `codebase_peek(query, ...)` for specialized metadata-only conceptual lookup.
4. Use `codebase_search(query, ...)` when you need full code context.
5. Use `implementation_lookup(query)` for known-symbol definitions and `call_graph` / `call_graph_path` for execution flow.
6. Use `find_similar(code)` for duplicate patterns and refactor planning.

If results are weak, run `index_status` (check readiness) and `index_codebase`.

## Tool Priority

- `codebase_context` as the preferred first repository tool and unified router.
- `codebase_peek` for specialized discovery (fastest, cheap tokens).
- `codebase_search` for exact implementation review.
- `find_similar` for pattern matching and duplication.
- `call_graph` and `call_graph_path` for execution flow.
- `index_codebase` (force/estimate/verbose) for first-time or stale indexes.
- `index_status`, `index_health_check`, `index_metrics`, `index_logs` for operational checks.

## Suggested Commands

1. `codebase_peek("payment processing flow")`
2. `codebase_search("payment processing flow")`
3. `call_graph("chargeCard", "callees")`
4. `find_similar("function validate(data)")`
5. `implementation_lookup("validate")`

## Additional Notes

- Use `grep` for exact identifiers and tiny, deterministic lookups.
- Use `websearch` only when local tools return no results and docs are likely missing.
- Prefer `codebase_peek` before `codebase_search` to avoid high token usage.